Limit the number of chained exceptions included in formatted traceback
Open
Nobody has claimed this yet.
3.11
interpreter-core
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45694 |
|---|---|
| Nosy | @gvanrossum, @iritkatriel |
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 2021-11-02.19:01:34.685>
labels = ['interpreter-core', 'type-feature', 'library', '3.11']
title = 'Limit the number of chained exceptions included in formatted traceback'
updated_at = <Date 2021-11-03.22:21:16.464>
user = 'https://github.com/iritkatriel'
bugs.python.org fields:
activity = <Date 2021-11-03.22:21:16.464>
actor = 'gvanrossum'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Library (Lib)']
creation = <Date 2021-11-02.19:01:34.685>
creator = 'iritkatriel'
dependencies = []
files = []
hgrepos = []
issue_num = 45694
keywords = []
message_count = 1.0
messages = ['405533']
nosy_count = 2.0
nosy_names = ['gvanrossum', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue45694'
versions = ['Python 3.11']
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 45694 and the CPython traceback-formatting implementation; no source file, test, or entry point is named in this issue. Clarify the intended limit for chained exceptions, then identify the relevant tests and implementation area. Done means the agreed limit is enforced in formatted tracebacks with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100