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

Matplotlib backend issue (TkAgg)

Open
#1,652 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
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
matplotlib, python
Domain
devtools

Research direction

Start by reproducing the blank, unresponsive TkAgg figure in the VS Code debugger using Python 3.9.5, Matplotlib 3.9.1–3.9.2, and VS Code 1.92.1. Compare the debugger behavior and reported backend with normal script execution, and review the linked Matplotlib issue; done when the cause of the backend discrepancy and debugger-specific plotting behavior is identified.

Written by the indexing model from the issue text.

Description

bug

Hey, I am having an issue plotting stuff in the debugger.

When I import matplotlib and print the backend, the output is 'tkagg'.
When I try to plot something, I will get an unresponsive blank figure (unless i call pause which will make desired plot appear but albeit remain unresponsive). When I set backend to 'TkAgg', it works as expected.

When I run the script normally not in the debugger, everything works fine and the plot appears.

What is weird is that my colleague has the same versions of python matplotlib and vs code yet by default has a backend of 'TkAgg'.
I am not sure what's causing this discrepancy in default backend between the two of us. In any case, according to matplotlib documentation and the linked issue, tkagg and TkAgg should be equivalent.

Relevant issue: Matplotlib
VS Code version: 1.92.1
Python: 3.9.5
Matplotlib: (3.9.1 - 3.9.2)

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.