having a PriorityQueue in multiprocessing.queue module like in queue module would be a plus
Open
Nobody has claimed this yet.
3.11
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38259 |
|---|
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-09-23.14:43:00.774>
labels = ['type-feature', '3.9']
title = 'having a PriorityQueue in multiprocessing.queue module like in queue module would be a plus'
updated_at = <Date 2020-01-10.12:45:19.630>
user = 'https://bugs.python.org/YairBonastre'
bugs.python.org fields:
activity = <Date 2020-01-10.12:45:19.630>
actor = 'Yair Bonastre'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-09-23.14:43:00.774>
creator = 'Yair Bonastre'
dependencies = []
files = []
hgrepos = []
issue_num = 38259
keywords = []
message_count = 1.0
messages = ['353022']
nosy_count = 1.0
nosy_names = ['Yair Bonastre']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue38259'
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 by comparing the existing queue.PriorityQueue API with the multiprocessing.queue module and inspect the module's current tests. Determine the expected multiprocessing equivalent and add coverage for the supported PriorityQueue behavior; done means the feature is available through multiprocessing.queue and its tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100