Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

FEAT: Support ipython's `_repr_*_()` protocol

Open
#1,563 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, vscode

Research direction

The issue names no files or tests; first reproduce the rich table example in an IPython terminal and in the VS Code debugger, then compare how each handles IPython's repr*_() protocol. Done means supported rich-display representations appear in the debugger instead of the default object repr.

Written by the indexing model from the issue text.

Description

I often work with objects that support ipython's _repr_*_() protocol, such as rich objects. For example, Ibis returns rich tables as an output format.

If you run this in an ipython terminal, you get nice output:

from rich.__main__ import make_test_card
make_test_card()

but in the vscode debugger, you just get <rich.table.Table object at 0x13cb9b550>\

Can we use ipython instead of the vanilla interpreter? Or something else to make debugging more ergonomic?

Dominant language
Python
Stars
2.5k
Forks
202
Avg merge
5d 1h
Merged PRs (30d)
1

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 microsoft/debugpy

All issues in microsoft/debugpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.