contextvars documentation unclear on thread-locality
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36359 |
|---|---|
| Nosy | @1st1 |
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-03-19.07:26:24.308>
labels = ['3.8', 'type-feature', '3.7', 'docs']
title = 'contextvars documentation unclear on thread-locality'
updated_at = <Date 2019-03-19.07:26:24.308>
user = 'https://bugs.python.org/HameerAbbasi2'
bugs.python.org fields:
activity = <Date 2019-03-19.07:26:24.308>
actor = 'Hameer Abbasi2'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2019-03-19.07:26:24.308>
creator = 'Hameer Abbasi2'
dependencies = []
files = []
hgrepos = []
issue_num = 36359
keywords = []
message_count = 1.0
messages = ['338322']
nosy_count = 3.0
nosy_names = ['docs@python', 'yselivanov', 'Hameer Abbasi2']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue36359'
versions = ['Python 3.7', '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 reading the contextvars documentation and the linked BPO issue 36359, focusing on the unclear explanation of thread-locality. Identify the relevant documentation section and clarify how context variables relate to thread-local behavior, then verify that the explanation is accurate for Python 3.7 and 3.8.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100