Python not reentrant
Open
Nobody has claimed this yet.
3.8 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34707 |
|---|---|
| Nosy | @ncoghlan, @vstinner, @ericvsmith, @ericsnowcurrently, @skaller |
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-17.02:04:35.399>
labels = ['interpreter-core', 'type-bug', '3.8']
title = 'Python not reentrant'
updated_at = <Date 2018-09-17.15:54:30.389>
user = 'https://github.com/skaller'
bugs.python.org fields:
activity = <Date 2018-09-17.15:54:30.389>
actor = 'eric.snow'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2018-09-17.02:04:35.399>
creator = 'skaller'
dependencies = []
files = []
hgrepos = []
issue_num = 34707
keywords = []
message_count = 4.0
messages = ['325508', '325524', '325527', '325549']
nosy_count = 5.0
nosy_names = ['ncoghlan', 'vstinner', 'eric.smith', 'eric.snow', 'skaller']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34707'
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
The payload names no files, tests, or entry points; begin with BPO 34707 and its four migrated messages to recover the failing reentrancy scenario. Identify the interpreter component involved, a reproducible test case, and the expected behavior; done means the test passes without regressing existing interpreter tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100