Deal better with StackOverflow exception when debugging
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
interpreter-core
type-crash
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38023 |
|---|
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-09-04.00:18:43.244>
labels = ['interpreter-core', '3.7', '3.8', '3.9', 'type-crash']
title = 'Deal better with StackOverflow exception when debugging'
updated_at = <Date 2019-09-04.00:18:43.244>
user = 'https://bugs.python.org/almenonanon'
bugs.python.org fields:
activity = <Date 2019-09-04.00:18:43.244>
actor = 'almenon anon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2019-09-04.00:18:43.244>
creator = 'almenon anon'
dependencies = []
files = []
hgrepos = []
issue_num = 38023
keywords = []
message_count = 1.0
messages = ['351107']
nosy_count = 1.0
nosy_names = ['almenon anon']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue38023'
versions = ['Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9']
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
No source file, test, entry point, or reproduction is provided. Start by reading the migrated issue at bugs.python.org/issue38023 and establish how the StackOverflow exception appears while debugging. Done should mean the intended debugging behavior is agreed and covered by a reproducible test.
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
- 20/100