multiprocessing.dummy missing cpu_count
Open
Nobody has claimed this yet.
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 29868 |
|---|---|
| Nosy | @vstinner, @florentx, @applio, @wiseman |
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 2017-03-21.22:59:06.435>
labels = ['type-bug', 'library']
title = 'multiprocessing.dummy missing cpu_count'
updated_at = <Date 2017-07-04.10:48:25.906>
user = 'https://github.com/wiseman'
bugs.python.org fields:
activity = <Date 2017-07-04.10:48:25.906>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-03-21.22:59:06.435>
creator = 'johnwiseman'
dependencies = []
files = []
hgrepos = []
issue_num = 29868
keywords = []
message_count = 2.0
messages = ['289950', '297640']
nosy_count = 4.0
nosy_names = ['vstinner', 'flox', 'davin', 'johnwiseman']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29868'
versions = ['Python 3.6']
Linked PRs
- gh-110717
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 concerns multiprocessing.dummy and its missing cpu_count; start by inspecting that module and comparing it with the existing multiprocessing implementation. Review linked PR gh-110717, and consider the issue done when multiprocessing.dummy provides the expected cpu_count behavior with appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100