Tracebacks are unnecessarily verbose when using 'python -m'

Open
#60,421 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
developer-experience

Research direction

Reproduce the verbose traceback through the python -m entry point and review the linked bpo-31299 dependency concerning TracebackException.format() and its ignore_modules option. Determine the intended reduction in traceback output and add coverage for the resulting behavior; the issue is done when python -m no longer includes the unnecessary frames.

Written by the indexing model from the issue text.

Description

3.7 (EOL) stdlib type-feature
BPO 16217
Nosy @ncoghlan, @mattheww, @ezio-melotti, @ericsnowcurrently, @vaultah
Dependencies
  • bpo-31299: Add "ignore_modules" option to TracebackException.format()
    		•

    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 2012-10-13.12:51:40.918>
labels = ['3.7', 'type-feature', 'library']
title = "Tracebacks are unnecessarily verbose when using 'python -m'"
updated_at = <Date 2020-01-29.00:38:55.074>
user = 'https://github.com/mattheww'

    bugs.python.org fields:

    activity = <Date 2020-01-29.00:38:55.074>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2012-10-13.12:51:40.918>
creator = 'mattheww'
dependencies = ['31299']
files = []
hgrepos = []
issue_num = 16217
keywords = []
message_count = 8.0
messages = ['172806', '172808', '245898', '300711', '300742', '300959', '300975', '300978']
nosy_count = 6.0
nosy_names = ['ncoghlan', 'mattheww', 'ezio.melotti', 'Arfrever', 'eric.snow', 'vaultah']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue16217'
versions = ['Python 3.7']

    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.