Python 2.7 interpreter missing from interpreter list and global environment list

[ltan10]

Python 2.7 is missing from global environment and interpreter list.

I understand that python 2 is no longer officially supported by vscode-ms-python.
There are still people who maintain a code base for python2, including myself and it it has still always been an option to select and use python 2.7 as an interpreter.

vscode version: 1.97.2
Also tried different python vscode extensions
python ext: 2025.0.0 and 2025.1.2025022501 (pre-release)

The following test cases were performed with various environment managers enabled:
Vscode restarted between cases

	No Environment Manager	donjayamanne.python-environment-manager	ms-python.vscode-python-envs	donjayamanne.python-environment-manager + ms-python.vscode-python-envs
Listed in interpreter selection	Y	Y	N	N
Switchable from interpreter selection	Y	Y	*N/A	*N/A
Listed in env manager (global)	*N/A	Y	N	N
Switchable env manager (global)	*N/A	Y	*N/A	*N/A

* Not applicable due to option is not listed thus able to be selected

From the above cases, it appears that ms-python.vscode-python-envs extension is actively delisting python 2.7 from the list of interpreters and global env within vscode.

[karthiknadig]

Thanks for reaching out! You're right that the Python extension no longer officially supports Python 2.7 due to maintenance and security concerns. The ms-python.vscode-python-envs extension follows this policy, which is why Python 2.7 interpreters are not listed by default.

That said, one of the goals of this extension is to enable the community to build their own environment management solutions. If you still need Python 2.7 support, you could create a community extension that adds it back using the provided environment APIs. Other extensions that rely on the Python extension (such as debugger and tools extensions) will recognize the interpreter path, provided you pin them to compatible extension versions. One of the reasons we split the debugger into its own extension is to allow pinning when working with legacy python versions.

If you're interested, I can provide code examples and details on how to create an extension from scratch. The "system Python" implementation is quite close to your needs, so you can mostly adopt it with some adjustments. I'm happy to help if you have any questions!

[ltan10]

Thanks for your response.
My understanding with regards to being able to select python2.7 as an interpreter is being supported by vscode-python extension, hence i raised this issue.

Which as observed in the test cases in the original post.
If i disabled the ms-python.vscode-python-envs environment manager extension and all other environment manager extension, i am able to select python 2.7 as an interpreter. And i am referring to selecting the interpreter either from the command palette or the interpreter list from the status bar in bottom right corner.

Which is in support of documentation for vscode-python extention.
https://github.com/microsoft/vscode-python/wiki/Limited-support-for-Python-2.7

For auto-completion, you can turn off auto-completions, or select Pylance as your language server as it may provide a good experience if the code is compatible enough with Python 3. We will continue to support selecting Python 2.7 as an interpreter in your workspace. For tools that keep support for Python 2.7 in their actively maintained version, we will continue to support using them with Python 2.7.

Thus to observe the microsoft python environment manager ms-python.vscode-python-envs actively filtering out python2.7 was a suprise. As ms-python.vscode-python-envs is an environment manager, it should not actively filter and alter the the interpreters list from vscode-python. And if the manager can't support managing python2.7, so be it. Just not actively remove the ability to select python2.7 as an interpreter.

Summary:
Just for interpreter list to not being mangled by ms-python.vscode-python-envs and able to select python2.7 as interpreter.

On a side note:
I would be interested in the resources you could provide with regards to extension development.

[karthiknadig]

As ms-python.vscode-python-envs is an environment manager, it should not actively filter and alter the the interpreters list from vscode-python

When you install ms-python.vscode-python-envs the vscode-python uses the environments extension for discovery, activation and execution. Hence my recommendation to contribute a legacy environments provider. If you do that, it will automatically integrate with the rest of the flow.

I would be interested in the resources you could provide with regards to extension development.

Details on how to create your own extension here:
https://github.com/microsoft/vscode-python-environments/blob/main/examples/README.md

You can pretty much copy the contents of : https://github.com/microsoft/vscode-python-environments/tree/main/examples into a separate repo and add your legacy implementation there.

To publish your extension to the marketplace you will need a account here: https://marketplace.visualstudio.com/vscode

If you do start working on this let me know, and I can help.