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]

+1 Add support, please

[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.