Support Poetry depenedency manager

[jared-mackey]

Currently it looks like Pipenv is supported but not poetry. Is there plans to support this dependency manager as well?

Note:

Activating poetry environments do not work (at least not yet).
python-poetry/poetry#198
python-poetry/poetry#571

[brettcannon]

No specific plans at the moment, but if people begin to vote for this issue with a 👍 reaction then we will definitely consider it.

[brettcannon]

We are going to wait until poetry hits version 1.0 before making a decision about this. People should continue to leave a 👍 reaction on the top comment until then to help us prioritize a decision and potential work compared to other feature requests.

[kevinpostal]

One workaround is to use virtualenvs in project root. Then vscode picks it up.
poetry config settings.virtualenvs.in-project true

[qubitron]

We are looking at implementing this, so I want to clarify the desired behavior here: if Poetry is detected in the current environment, prompt user if they want to install packages (pylint, rope, etc) using poetry.

Is that correct? Please let us know if there's additional behavior desired here.

[leos]

Any installations should happen via poetry. It would also be great if VS Code could autodetect the poetry virtualenv and use it.

[lig]

@qubitron personally, I found poetry's lack of interpreter version management ability a bit frustrating. I believe this should be addressed in the implementation somehow. Comparing to pipenv's ability to choose an interpreter version to create the environment based on Pipfile, poetry always uses the default interpreter to create the environment and could fail if the version is incompatible with the requirement defined in pyproject.toml.

[DonJayamanne]

I believe this should be addressed in the implementation somehow.

Activating poetry environments do not work (at least not yet).
python-poetry/poetry#198
python-poetry/poetry#571

If things don't work in the tool itself, we're not going to try to add workarounds or implement solutions.

What can be done however is just add support for using poetry, when the extension prompts users to install any python packages. We do this today for conda, pipenv, environments.

I.e. when user needs to install a formatter, we'll (optionally) make use of poetry.

[brettcannon]

@lig since we do not manage environment creation that will be out of scoped for this work.

[abhishekvm]

We are looking at implementing this, so I want to clarify the desired behavior here: if Poetry is detected in the current environment, prompt user if they want to install packages (pylint, rope, etc) using poetry.

Is that correct? Please let us know if there's additional behavior desired here.

Till the time support for poetry gets added, I was thinking if there is any hacky way we can get through this. vscode installs any packages with following command:
<PYTHONPATH>python -m pip install -U pytest or <PYTHONPATH>python -m pip install -U pylint

Is there any way in vscode where we can map pip install to poetry add --dev?

[brettcannon]

@abhishekvm nope, we don't provide that kind of functionality. You can always do the install manually while people wait for this feature since as you noticed we aren't doing anything too magical.

[DonJayamanne]

• Create PoetryInstaller similar to pipEnvInstaller etc (https://github.com/Microsoft/vscode-python/blob/ae1848a82f5af8983f663d5d4db2c4f77ad62c57/src/client/common/installer/pipEnvInstaller.ts)
• Check whether we prompt to install using pipenv or pip, similarly display prompt
• Add settings poetryPath in settings.json
• Use poetry only if the corresponding lock file is available.

[ericsnowcurrently]

I was able to verify that poetry is used to install modules:

1. python -m pip install --user poetry
2. in project: python -m poetry init
3. in project: python -m poetry lock
4. workspace settings: "python.linting.flake8enabled": true
5. reload window

This caused the popup for installing flake8. Then poetry was used to install flake8.