Documented interaction of single-stage init and sub-interpreters inaccurate
Open
Nobody has claimed this yet.
3.10
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42298 |
|---|---|
| Nosy | @yol |
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 2020-11-09.17:51:42.034>
labels = ['3.7', '3.8', '3.9', '3.10', 'docs']
title = 'Documented interaction of single-stage init and sub-interpreters inaccurate'
updated_at = <Date 2020-11-09.17:51:42.034>
user = 'https://github.com/yol'
bugs.python.org fields:
activity = <Date 2020-11-09.17:51:42.034>
actor = 'pkerling'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2020-11-09.17:51:42.034>
creator = 'pkerling'
dependencies = []
files = []
hgrepos = []
issue_num = 42298
keywords = []
message_count = 1.0
messages = ['380602']
nosy_count = 2.0
nosy_names = ['docs@python', 'pkerling']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue42298'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10']
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 locating the CPython documentation describing single-stage initialization and sub-interpreters, then compare its stated interaction with the behavior discussed in BPO 42298. Done means the relevant documentation accurately explains that interaction; the issue does not name a file or test to run.
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
- 35/100