multiprocessing: add SharedMemory.rename() -- shm_rename() FreeBSD support

Open
#90,556 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start by reviewing the linked work in python/cpython#30621 and gh-132130, then trace the existing multiprocessing SharedMemory implementation and its platform-specific support. Done means FreeBSD support for the requested SharedMemory.rename() and shm_rename behavior, with the relevant tests updated or passing.

Written by the indexing model from the issue text.

Description

extension-modules OS-freebsd topic-multiprocessing type-feature
BPO 46398
Nosy @vstinner, @koobs, @devnexen
PRs
  • python/cpython#30621
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2022-01-16.13:51:26.292>
labels = ['type-feature']
title = 'posixshmem module shm_rename freebsd support.'
updated_at = <Date 2022-01-16.13:52:36.453>
user = 'https://github.com/devnexen'

    bugs.python.org fields:

    activity = <Date 2022-01-16.13:52:36.453>
actor = 'devnexen'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['FreeBSD']
creation = <Date 2022-01-16.13:51:26.292>
creator = 'devnexen'
dependencies = []
files = []
hgrepos = []
issue_num = 46398
keywords = []
message_count = 1.0
messages = ['410694']
nosy_count = 3.0
nosy_names = ['vstinner', 'koobs', 'devnexen']
pr_nums = ['30621']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46398'
versions = []

    Linked PRs
    • gh-132130
    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.