create multiprocessing.SharedMemory by pointing to existing memoryview
Open
Nobody has claimed this yet.
3.13
performance
stdlib
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39767 |
|---|
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 2020-02-26.23:46:31.295>
labels = ['3.8', 'library', 'performance']
title = 'create multiprocessing.SharedMemory by pointing to existing memoryview'
updated_at = <Date 2021-06-22.14:43:45.738>
user = 'https://bugs.python.org/DariuszTrawinski'
bugs.python.org fields:
activity = <Date 2021-06-22.14:43:45.738>
actor = 'petr.viktorin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-02-26.23:46:31.295>
creator = 'Dariusz Trawinski'
dependencies = []
files = []
hgrepos = []
issue_num = 39767
keywords = []
message_count = 1.0
messages = ['362754']
nosy_count = 1.0
nosy_names = ['Dariusz Trawinski']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue39767'
versions = ['Python 3.8']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names multiprocessing.SharedMemory as the entry point; start there and inspect how its constructor currently obtains memory. Done means it can be created by pointing at an existing memoryview, with the behavior verified by the relevant library tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100