Provide debuggers with a way to know that a function is exiting with an unhandled exception.
Open
Nobody has claimed this yet.
3.8 (EOL)
interpreter-core
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 34099 |
|---|---|
| Nosy | @fabioz, @ericsnowcurrently |
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-07-11.18:07:01.401>
labels = ['interpreter-core', 'type-feature', '3.8']
title = 'Provide debuggers with a way to know that a function is exiting with an unhandled exception.'
updated_at = <Date 2018-07-11.19:39:46.100>
user = 'https://github.com/fabioz'
bugs.python.org fields:
activity = <Date 2018-07-11.19:39:46.100>
actor = 'eric.snow'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2018-07-11.18:07:01.401>
creator = 'fabioz'
dependencies = []
files = []
hgrepos = []
issue_num = 34099
keywords = []
message_count = 1.0
messages = ['321492']
nosy_count = 2.0
nosy_names = ['fabioz', 'eric.snow']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue34099'
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 with BPO issue 34099 and its recorded discussion; the payload names no source files, tests, or entry points. Before implementation, establish the debugger-facing behavior and a testable completion condition, then document those in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100