GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add documentation for new `colorize` keyword argument in traceback documentation · Issue #142896 · python/cpython

Add documentation for new colorize keyword argument in traceback documentation #142896

New issue
Copy link
New issue
Copy link
Closed as not planned
Closed as not planned
Add documentation for new colorize keyword argument in traceback documentation#142896
Copy link
Labels
docsDocumentation in the Doc dirDocumentation in the Doc dir

Description

@mccullerlp
mccullerlp
opened on Dec 17, 2025
Issue body actions

Documentation of Traceback module colorize features

The new colorized tracebacks are awesome. When users manually create tracebacks using the traceback module, they will not get colorized output by default.

This is because the colorize=True argument needs to be passed to the traceback.print_exception function.

This argument isn't in the documentation. I found it by reading the diffs on the traceback colorization PR.

#112730

Activity

  1. mccullerlp
    added
    docsDocumentation in the Doc dirDocumentation in the Doc dir
    on Dec 17, 2025
  2. github-project-automation
    added this to docs issueson Dec 17, 2025
  3. github-project-automation
    moved this to Todo in docs issueson Dec 17, 2025
  4. pablogsal commented on Dec 17, 2025

    @pablogsal
    pablogsal
    on Dec 17, 2025
    Member
    More actions

    Unfortunately the reason the code is structured as it is is to keep that argument private to the stdlib. The colorization story is still ongoing so we are not ready to open this for public consumption in case we need to change it in the future. Thanks for your understanding

    Reacted by Stan Ulbrych
  5. pablogsal
    closed this as not plannedon Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation in the Doc dirDocumentation in the Doc dir

    Projects

    • docs issues
      Status
      Todo
      Show more project fields

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.