Documentation: Clarify role of callback with map_async
Open
Nobody has claimed this yet.
docs
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29108 |
|---|---|
| Nosy | @applio |
| 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 2016-12-29.21:57:31.364>
labels = ['type-bug', 'docs']
title = 'Documentation: Clarify role of callback with map_async'
updated_at = <Date 2020-09-18.16:03:49.957>
user = 'https://bugs.python.org/JoseMiguelColella'
bugs.python.org fields:
activity = <Date 2020-09-18.16:03:49.957>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2016-12-29.21:57:31.364>
creator = 'Jose Miguel Colella'
dependencies = []
files = ['46084']
hgrepos = []
issue_num = 29108
keywords = []
message_count = 4.0
messages = ['284295', '284296', '284305', '284320']
nosy_count = 3.0
nosy_names = ['docs@python', 'davin', 'Jose Miguel Colella']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29108'
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
Read the Python documentation for map_async and inspect the linked main2.py example to understand how its callback is used. Clarify the callback's role in the map_async documentation, then verify that the resulting text answers the reported behavior question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100