Repository navigation
Bring back Python 3.6 debugging support by breaking debugging out into its own extension #19559
Description
By making debugging a separate extension we can do an initial release using debugpy 1.5 which will work all the way back to Python 2.7, and then immediately do another release using debugpy 1.6. That way people who need debugging support for older Python versions can pin the debugging extension version but leave the Python extension alone to get newer feature support (if it works with the old version of Python that they are running).
Activity
[-]Break out debugging support into its own extension[/-][+]Break out debugging support into its own extension (to support Python 3.6 debugging)[/+][-]Break out debugging support into its own extension (to support Python 3.6 debugging)[/-][+]Bring back Python 3.6 debugging support by breaking debugging out into its own extension[/+]aamarin commentedon Oct 15, 2022
Is this only for debugging support? Or can Intellisense also be included? I work for a company that uses Red Hat 7 which does support 3.6 as part of the distribution.
brettcannon commentedon Oct 17, 2022
This is only explicitly for debugging as IntelliSense shouldn't be affected by any of this as Pylance is written in TypeScript. If you're using Jedi then that is up to the Jedi project itself in terms of what versions they support.
nutu commentedon Dec 16, 2022
I am feeling that this answers my question on why my debugger does not start: https://stackoverflow.com/questions/74812777/vs-code-python-debugger-would-not-start-with-python-extension-2022-xx-xx-althoug?noredirect=1#comment132043707_74812777
What is the minimal python version that still works with the python extension debugger?
brettcannon commentedon Dec 19, 2022
Python 3.7.
yanjieee commentedon Mar 20, 2023
v2022.6.3 working fine
GitMensch commentedon Apr 11, 2023
Is there any ETA? I'm regularly hit by the update / new install then later wonder why something doesn't work on a remote...
Additional this would make the Python extension itself smaller which is nice for people that don't actually need to debug.
... and wouldn't this issue be still the same, so Python 2.7 still won't work (last time it did was v2022.2.x, I think)?
brettcannon commentedon Apr 11, 2023
Simon Sobisch (@GitMensch) no promises, but we are hoping for a preview release in May.
And Python 2.7 is in the same situation as 3.6, so we would have to see if the last debugpy release would work with the extension and then make that the initial release, do an immediate new release for one that uses the newest version that supports back to Python 3.6, and then do yet another immediate release that uses the newest version of debugpy regardless of Python version support. But once again, no promises on whether we will be able to get support for Python 2.7 out.
32 remaining items
DoctorYi commentedon Feb 5, 2024
brettcannon commentedon Feb 5, 2024
Unfortunately I can't read that.
DoctorYi commentedon Feb 6, 2024
I tried to install another old version of debugger as advised( Search for debugpy again in the Extensions sidebar. Once again, select "Install another version". Choose v2023.1.12492010), but could not find the version any more
brettcannon commentedon Feb 6, 2024
There was a bug in the marketplace. Please try again.
DoctorYi commentedon Feb 6, 2024
stavnahumg commentedon Feb 11, 2024
Same here vscode : 1.84.2 won't show the 2023.X debugpy versions
stavnahumg commentedon Feb 12, 2024
still only v2024 available, got any info on this behaviour ?
paulacamargo25 commentedon Feb 12, 2024
You can follow the steps here in order to install a pre-release version of the extension.
brettcannon commentedon Feb 13, 2024
A detail that I'm not sure is obvious is you need to opt into the pre-release version of the extension as the older versions of the extension w/ older debugpy releases were released as pre-release. As soon as you switch you will see all of the versions:
(Notice how I filtered the versions to only "2023.1" and you can sort of make out behind the drop-down it says "Switch to Release Version", showing I'm using a pre-release version.)
brettcannon commentedon Feb 13, 2024
I have opened microsoft/vscode-python-debugger#212 to help make this more clear.
paulacamargo25 commentedon Jun 26, 2024
I'll close this issue since the Python Debugger is already in production, feel free to submit a feature-request pr bug report in the Python Debugger Extension Repository.
DoctorYi commentedon Jun 26, 2024