Cannot pass a SyncManager proxy to a multiprocessing subprocess on Windows
Open
Nobody has claimed this yet.
OS-windows
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33088 |
|---|---|
| Nosy | @pfmoore, @pitrou, @tjguk, @zware, @zooba, @applio |
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 2018-03-16.18:10:25.896>
labels = ['type-bug', 'OS-windows']
title = 'Cannot pass a SyncManager proxy to a multiprocessing subprocess on Windows'
updated_at = <Date 2018-03-16.20:08:00.306>
user = 'https://bugs.python.org/jjdmon'
bugs.python.org fields:
activity = <Date 2018-03-16.20:08:00.306>
actor = 'ned.deily'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2018-03-16.18:10:25.896>
creator = 'jjdmon'
dependencies = []
files = []
hgrepos = []
issue_num = 33088
keywords = []
message_count = 1.0
messages = ['313964']
nosy_count = 7.0
nosy_names = ['paul.moore', 'pitrou', 'tim.golden', 'zach.ware', 'steve.dower', 'davin', 'jjdmon']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33088'
versions = ['Python 3.6']
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 no files, tests, or entry points beyond Windows multiprocessing and SyncManager proxies. Start by reproducing the failure on Python 3.6 with a Windows subprocess, then trace the multiprocessing and manager-proxy paths; done means the proxy can be passed successfully and the behavior is covered by a regression test.
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