Multiprocessing does not work properly when using the trace module.
Open
Nobody has claimed this yet.
3.9 (EOL)
OS-windows
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38511 |
|---|---|
| Nosy | @pfmoore, @tjguk, @zware, @zooba, @rls1004 |
| Files |
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 2019-10-18.06:54:41.871>
labels = ['type-bug', '3.9', 'OS-windows']
title = 'Multiprocessing does not work properly when using the trace module.'
updated_at = <Date 2019-10-18.11:46:53.991>
user = 'https://github.com/rls1004'
bugs.python.org fields:
activity = <Date 2019-10-18.11:46:53.991>
actor = '\xd8\xaa\xd8\xa7\xd8\xb4\xd9\x8a\xd8\xb1\xd8\xa7\xd8\xaa \xd9\x85\xd8\xb3\xd8\xa7\xd9\x86\xd8\xaf'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2019-10-18.06:54:41.871>
creator = 'rls1004'
dependencies = []
files = ['48667']
hgrepos = []
issue_num = 38511
keywords = []
message_count = 2.0
messages = ['354864', '354879']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'steve.dower', 'rls1004', '\xd8\xaa\xd8\xa7\xd8\xb4\xd9\x8a\xd8\xb1\xd8\xa7\xd8\xaa \xd9\x85\xd8\xb3\xd8\xa7\xd9\x86\xd8\xaf']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38511'
versions = ['Python 3.9']
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
Start with the attached test.py reproduction and run it on Windows with Python multiprocessing and the trace module enabled. Read the trace and multiprocessing entry points involved in the failure, then verify that the reproduction completes correctly with tracing enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100