Globally disable installing `pytest` if missing

[adament]

I spend a frustraring amount of time and mental energy having to uninstall packages that this extension "helpfully" installed for me, such as pytest or ipykernel. Would it be possible to add a global toggle to disable this behaviour? I.e. for the extension to only ever advise about missing packages such as pytest and ipykernel and never call out to conda install or similar?

I want to manage my own environments, and make sure that the environment is only changed when I intended to do it. It surprises me everytime this extension feels entitled to modify my environments, and 9 times out 10, I did not want that extension installed and it was only missing because I had the wrong environment activated.

[karthiknadig]

In this extension we only pytest if testing is enabled and it is missing. I agree it should ask before installing pytest.

For ipykernel please file a bug on the Jupyter extension.

[karthiknadig]

Can you provide details of the extension version installed? It seems like this might actually be a bug.

[adament]

I am very sorry, I forgot that of course it is the jupyter extension that installs ipykernel, I will report that there.

As for pytest it just happened to me again when I wanted to configure python testing and as part of that configuration pytest was installed without further confirmation than just choosing pytest as framework and choosing the test folder. Because I had forgotten to activate the correct environment for a newly cloned repository.

Is it relevant that the incorrectly active environment was a pixi environment?

I currently have 2024.222 installed:

ms-python.debugpy@2024.14.0
ms-python.python@2024.22.2
ms-python.vscode-pylance@2024.12.1
ms-toolsai.jupyter@2024.11.0
ms-toolsai.jupyter-keymap@1.1.2
ms-toolsai.jupyter-renderers@1.0.21
ms-toolsai.vscode-jupyter-cell-tags@0.1.9
ms-toolsai.vscode-jupyter-slideshow@0.1.6

[eleanorjboyd]

Hi @adament - thanks for submitting the issue!

Going to approach this in a few parts- long term we are moving to this new environments extension and will have a whole flow there that we need to iterate on for package approval and notification of installation. see here

in the meantime I am going to look into why its being triggered too much and add a notification. I will work on this and update this issue as I go. Thanks