traceback: formatting a traceback stats the filesystem

Open
#67,462 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the migrated BPO issue 23273 linked in the body, since this issue names no files, tests, reproduction steps, or expected behavior. Establish a reproducible case for traceback formatting accessing the filesystem, then identify the relevant traceback implementation and tests; done means the behavior is corrected and covered by a regression test.

Written by the indexing model from the issue text.

Description

stdlib
BPO 23273
Nosy @rbtcollins

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 2015-01-19.17:55:08.429>
labels = []
title = 'traceback: formatting a traceback stats the filesystem'
updated_at = <Date 2015-01-19.17:55:08.429>
user = 'https://github.com/rbtcollins'

bugs.python.org fields:

activity = <Date 2015-01-19.17:55:08.429>
actor = 'rbcollins'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2015-01-19.17:55:08.429>
creator = 'rbcollins'
dependencies = []
files = []
hgrepos = []
issue_num = 23273
keywords = []
message_count = 1.0
messages = ['234318']
nosy_count = 1.0
nosy_names = ['rbcollins']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue23273'
versions = []

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.