Stop auto install "Python Environments" ext. I really don't need it.

[ladyrick]

Stop auto install "Python Environments" ext. I really don't need it.

Recently you add "Python Environments" to your ext pack.
I really don't need it. I had to uninstall it manually after I upgrade "python" extension. That's annoying me.

[eleanorjboyd]

Hi! This is our new extension we will be moving towards using for all environment related actions. It will work under-the-hood to provide the correct environment info to the Python extension and we will remove all environment selection / create / find code in the Python extension to using this new extension. You can select to hide the Python icon in the side panel if you do not want to see it (like you don't want the UI), but the extension will be needed for basic actions moving forward.

[eleanorjboyd]

Let me know if hiding the icon would fix your problem or if you are seeing additional bugs. Thanks

[ladyrick]

Hi! This is our new extension we will be moving towards using for all environment related actions. It will work under-the-hood to provide the correct environment info to the Python extension and we will remove all environment selection / create / find code in the Python extension to using this new extension. You can select to hide the Python icon in the side panel if you do not want to see it (like you don't want the UI), but the extension will be needed for basic actions moving forward.

Thanks for your reply.

First of all

I need the feature of manually select python environment. I don't need to auto create a virtual env. If I need a virtual env, I'd like to create it in terminal by myself. And I don't need extensions to "auto activate" something (virtual env, in this case) when I open terminal. I want to keep my terminal simple.
So I don't need an environment manager extension. I suggest keep it embedded in "python" extension or remove from the suggested extension pack.

Time to complain

I don't like to do a job with too many extensions.
I don't want to make my vscode extension list like a node_modules.
If I had to install a set of extensions to do one job, why don't merge then together and simply call it "python"?

Very long ago, there is just one "python" extension.
But now, I need to install: "python", "black formatter", "flake8", "isort", "python debugger", and a "tensorboard" extension which seems dead.
Now you are going to add a "python environment" to the list.
This list is far too long.

Seriously, I really don't care an extension's large size. What I care is that this extension keep laying eggs (a lot of small extensions).

By the way, "jupyter" is also like an old hen laying many eggs:
"jupyter", "jupyter keymap", "jupyter slide show", "jupyter cell tags", "jupyter notebook renderers"
I can't help to guess that "jupyter" and "python" have a common father.
Also, there are "Remote - SSH" and "Remote - SSH: Editing Configuration Files". Wow, they made an individual extension to do a simple job: open .ssh/config, amazing.

My solution

I have already find a solution: add this to settings.json

  "extensions.allowed": {
    "*": true,
    "ms-python.vscode-python-envs": false,
    "ms-toolsai.vscode-jupyter-slideshow": false,
    "ms-toolsai.vscode-jupyter-cell-tags": false,
    "ms-toolsai.jupyter-keymap": false,
    "ms-toolsai.jupyter-renderers": false,
    "ms-vscode-remote.remote-ssh-edit": false
  }

[muellevin]

Thanks @ladyrick i didn't even noticed that it installed another extension.

I have a similiar problem as stated in #25430 and others have. Either the environment isn't found, blocking nearly everything or the interpreter selector spins indefinitely. Maybe it is worth adding in the FAQs for troubleshooting it? That way people still can get a fast workaround till it is fixed in another release.