Use coroutine object or coroutine function instead of coroutine
Open
Nobody has claimed this yet.
3.8 (EOL)
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34753 |
|---|---|
| Nosy | @1st1, @Windsooon |
| PRs |
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-09-20.15:22:10.069>
labels = ['type-feature', '3.8', 'docs']
title = 'Use coroutine object or coroutine function instead of coroutine'
updated_at = <Date 2018-09-24.05:11:58.864>
user = 'https://github.com/Windsooon'
bugs.python.org fields:
activity = <Date 2018-09-24.05:11:58.864>
actor = 'Windson Yang'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2018-09-20.15:22:10.069>
creator = 'Windson Yang'
dependencies = []
files = []
hgrepos = []
issue_num = 34753
keywords = ['patch']
message_count = 3.0
messages = ['325886', '325908', '325947']
nosy_count = 3.0
nosy_names = ['docs@python', 'yselivanov', 'Windson Yang']
pr_nums = ['9523']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue34753'
versions = ['Python 3.8']
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 reviewing the Python documentation references covered by BPO issue 34753 and the existing PR #9523. Search for uses of “coroutine” where the issue’s distinction between a coroutine object and coroutine function applies. Done means the relevant documentation uses the more precise terminology consistently.
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