python / python/cpython

Refactor traceback.py to make TracebackException more extensible.

Open
#89,321 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.11 stdlib type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 45158
Nosy @Abrosimov-a-a

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-09-09.22:41:24.200>
labels = ['type-feature', 'library', '3.11']
title = 'Refactor traceback.py to make TracebackException more extensible.'
updated_at = <Date 2021-09-09.23:05:39.751>
user = 'https://github.com/Abrosimov-a-a'

bugs.python.org fields:

activity = <Date 2021-09-09.23:05:39.751>
actor = 'abrosimov.a.a'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-09-09.22:41:24.200>
creator = 'abrosimov.a.a'
dependencies = []
files = []
hgrepos = []
issue_num = 45158
keywords = []
message_count = 2.0
messages = ['401528', '401529']
nosy_count = 1.0
nosy_names = ['abrosimov.a.a']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue45158'
versions = ['Python 3.11']

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading traceback.py and the TracebackException implementation. The issue does not identify specific entry points, tests, or desired extension points, so clarify the intended design before changing the refactor; done means TracebackException is demonstrably more extensible without changing existing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.