Stop asking which package manager to use for installing tools

[luabud]

Once we have support for poetry venvs, we can stop asking users which package manager to use when installing tools (e.g. linters, formatters, etc.)
If conda is selected, we try to use conda, if not we use pip
This would lead to less questions asked by the extension which could be annoying or even confusing.

[TBBle]

Now that #8372 is getting done, I assume that if a Poetry venv is activated, resolving this issue would mean that vscode-python would install its required packages via poetry add --dev rather than pip.

This is important because:

• Anything installed into the venv with pip is liable to be removed later by poetry install --remove-untracked, I think.
• Poetry 1.2.0 does not itself require pip or setuptools in the venv, and so at some point they will not exist: Control inclusion of pip and setuptools in virtual environments via config options python-poetry/poetry#3916 is discussing transitions and interactions with IDEs for this.

Edit: Actually this appears to already be the case.

[luabud]

@TBBle you're correct, this is already the case for Poetry, specifically 😊 if you try our Insiders build, you can see that we use Poetry to install packages if you have a Poetry environment selected.

[moracabanas]

I am on vscode 1.70.1
This is my case:
I generated a poetry .venv.
Then I created a vscode jupyter notebook.
It asks for install ipykernel dependencies and it does use poetry for that.

Then I try to format document so it ask for installing black:

But, the python output tab shows it is trying to use pip:

> . ./.venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-server/extensions/ms-python.python-2022.12.0/pythonFiles/printEnvVariables.py
> ./.venv/bin/python -c "import black"
> ./.venv/bin/python -c "import black"
> ./.venv/bin/python -c "import black"
> ./.venv/bin/python -c "import black"

Formatting with black failed.
You could either install the 'black' formatter, turn it off or use another formatter.
Error: Module 'black' not installed.
> ./.venv/bin/python -c "import black"

Formatting with black failed.
You could either install the 'black' formatter, turn it off or use another formatter.
Error: Module 'black' not installed.

Formatting with black failed.
You could either install the 'black' formatter, turn it off or use another formatter.
Error: Module 'black' not installed.

Formatting with black failed.
You could either install the 'black' formatter, turn it off or use another formatter.
Error: Module 'black' not installed.

Formatting with black failed.
You could either install the 'black' formatter, turn it off or use another formatter.
Error: Module 'black' not installed.
> ./.venv/bin/python -c "import pip"
> ./.venv/bin/python -c "import black"

So I notice Jupyter is using my .venv but the vscode python interpreter could be a different one.
I use Ctrl+Shift+p to select python interpreter and set it to my .vevn
So this way I got black installed and the installing output is now on the Terminal not on the Output tab:

 /home/becareo/python230/.venv/bin/python -m pip install -U black
Collecting black
  Using cached black-22.6.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.5 MB)

I hope I could get my visual studio to use Poetry add for everything and stop trying to randomly use PIP as a package manager.

Is there anything am I missing?
Thanks!

[luabud]

@moracabanas it seems like it could be the Python extension not recognizing your virtual environment as a poetry one. Would you mind opening a new issue following the instructions here and providing some more information?

In the mean time, we have a new Black Formatter extension that allows you to format your files without even needing to install Black on your environment, and It should also work on notebooks. If you end up trying it out, just make sure to run "Format document with..." and select "Black" instead of "Python"

[karrtikr]

Steps:

• Create a conda environment
• Use Python: Select linter command to select a linter.
• You'll see a prompt to install it.
• Ensure conda install command is used.