Add method class names in stack tracebacks

Open
#55,216 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue identifies CPython's Interpreter Core and stack tracebacks but names no file or test. Start by locating the traceback-generation entry point and reviewing the historical discussion; done means traceback frames include the relevant class name with focused regression coverage.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 11007
Nosy @terryjreedy, @amauryfa, @pitrou, @zware

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 2011-01-25.15:12:24.758>
labels = ['interpreter-core', 'type-feature', '3.10']
title = 'stack tracebacks should give the relevant class name'
updated_at = <Date 2020-11-04.18:17:04.776>
user = 'https://bugs.python.org/stickwithjosh'

bugs.python.org fields:

activity = <Date 2020-11-04.18:17:04.776>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2011-01-25.15:12:24.758>
creator = 'stickwithjosh'
dependencies = []
files = []
hgrepos = []
issue_num = 11007
keywords = []
message_count = 10.0
messages = ['127015', '127035', '127037', '127040', '127042', '127044', '127122', '130417', '283138', '283140']
nosy_count = 6.0
nosy_names = ['terry.reedy', 'amaury.forgeotdarc', 'pitrou', 'stickwithjosh', 'zach.ware', 'Winterflower']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue11007'
versions = ['Python 3.10']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

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.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.