Version compatibility problem

[algarit0]

Type: Bug

Behaviour

When launching the python debugger in version 3.9.13, it says that python debugger is not supported for versions minor than 3.9 (while the version is indeed bigger)

Steps to reproduce:

1. Have python 3.9.13 installed
2. Launch python debugger

Diagnostic data

launch.json configuration

XXX

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Output for Python Debugger in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python Debugger)

XXX

# Behaviour

XXX

Steps to reproduce:

1. XXX

Diagnostic data

launch.json configuration

XXX

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

Output for Python Debugger in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python Debugger)

XXX

Extension version: 2025.8.0
VS Code version: Code 1.100.1 (91fa95bccb027ece6a968589bb1d662fa9c8e170, 2025-05-09T15:43:50.040Z)
OS version: Windows_NT x64 10.0.26100
Modes:

• Python version (& distribution if applicable, e.g. Anaconda): 3.9.13
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda

System Info

Item	Value
CPUs	Intel(R) Core(TM) Ultra 7 155H (22 x 2995)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	31.46GB (13.45GB free)
Process Argv	--crash-reporter-id 37399409-4aac-4e63-a582-4adc93755fe3
Screen Reader	no
VM	0%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805cf:30301675
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
pythonrstrctxt:31112756
nativeloc1:31192215
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
c7cif404:31308204
31787653:31262186
3e8i5726:31271747
996jf627:31283433
pythonrdcb7cf:31303019
usemplatestapi:31297334
0aa6g176:31307128
7bj51361:31289155
747dc170:31275177
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
gendocf:31295004

[eleanorjboyd]

duplicate of #710

[algarit0]

Even if it is duplicate from #710, the original question isn't answered. If the minimum python version is 3.9, python 3.9.13 is still greater than 3.9 El mar, 27 may 2025 a las 20:31, Eleanor Boyd ***@***.***>) escribió:

…

Closed #712 <#712> as duplicate. — Reply to this email directly, view it on GitHub <#712 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3RGB3PWP2ML35AKXXHXXTL3ASVONAVCNFSM6AAAAAB5FPZ4QCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJXHAZTKOJZGQ3DAOA> . You are receiving this because you authored the thread.Message ID: ***@***.*** .com>

[eleanorjboyd]

Can you include logs or screenshots of the error message? It shouldn't be having that issue as its >= 3.9 so would need to see what you are seeing to understand it. Thanks

[gvellut]

I also have that issue on macOS with Python Debugger extension version 2025.8.0 and Python 3.9.22.

Here is the screenshot:

$ python --version
Python 3.9.22

The program launches and finishes but no breakpoint triggers.

[eleanorjboyd]

Im thinking there might be an issue where the selected python you have is different than the one in your terminal- if you go through the flow of "change python interpreter" are you able to select something that works? You could also use the command "select interpreter" in the command palette and try setting it here to make sure the version in your terminal is being used as your interpreter for vscode

[gvellut]

I ran the command in the terminal opened by the debugger.

I also ran the command the debugger ran ie from:
/usr/bin/env /Users/guilhem/Documents/projects/github/jncep/.venv/bin/python /Users/guilhem/.vscode/extensions/ms-python.debugpy-2025.8.0-darwin-arm64/bundled/libs/debugpy/adapter/../../debugpy/launcher ......

I ran :
/usr/bin/env /Users/guilhem/Documents/projects/github/jncep/.venv/bin/python --version

(the result is the same as python --version)

I did what you proposed:

• 'Python: Select interpreter'
• choose one of the 3.9.x ones
• I have the same popup

If I create a 3.10.x and select it then I don't have the popup message and the python version displayed in the terminal with --version is the 3.10.x one.

[algarit0]

Im thinking there might be an issue where the selected python you have is different than the one in your terminal- if you go through the flow of "change python interpreter" are you able to select something that works? You could also use the command "select interpreter" in the command palette and try setting it here to make sure the version in your terminal is being used as your interpreter for vscode

Thanks for your answer. No, the only python environments I have installed are a 3.12.7, the base environment (no problem here) and the only virtual environment i created

When I hit debug, the following message appears and the code runs normally, without taking into accound the debug breaking points:

[mvvitorsilvati]

@eleanorjboyd The correct thing here would not be just "< 9"?

See that the problem was caused in this PR:

https://github.com/microsoft/vscode-python-debugger/pull/705/files