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

Configure variables view presentation of `len()`

Open
#1,581 0 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
Domain
devtools

Research direction

Start by reviewing the issue's existing variablePresentation configuration and how the automatic len() entry appears in the variables view. Determine whether the requested behavior belongs in this project or in the surrounding debugger client. Done means a clearly specified, supported configuration for the requested presentation behavior.

Written by the indexing model from the issue text.

Description

So there is "variablePresentation" to configure hiding/grouping etc función kinds.

Note that there is no global way to set it yet https://github.com/microsoft/vscode-python-debugger/issues/165, but it can be done per launch config.

I was wondering if there was a way to configure the automomatic call to len() that appears at the end.
image

Something like:

  • Hiding it, i.g. reduce vertical space usage for many small lists
  • Moving it at the top, i.e. making it visible without having to open the collapsible region
  • Or a bit more involved config:
    • Showing it only when the full list of elements are hidden (over 100... etc) (bwt can this amount shown be configured?)
    • Move it to the top, but when the variable is expanded hide it from the list and replace the text next to the variable name (reduce redundant data):
      image

Probably there are other functions similar to len() that get called but I cannot recall right now.
So I guess those could be affected by these options too.

Best regards!

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.