Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How do I tell poetry to use python 2.7?

See original GitHub issue

The README indicates that poetry supports older versions of python, but when I run poetry install in a fresh project directory it’s using python 3 (the same one that poetry itself is running on). I can’t find an option to specify the python version to use. I specified python 2.7 as a dependency in my pyproject.toml.

Issue Analytics

State:
Created 5 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

5reactions

sdispatercommented, Apr 7, 2018

@radix Just to keep you posted.

The Python 2.7 support is coming along quite well. The only part remaining is the packaging/building part the rest is already supported (project creation and dependency installation).

So, expect full Python 2.7 support sometime next week 😃

1reaction

radixcommented, Apr 5, 2018

Supporting poetry running on python 2.7 would be excellent. It would mirror how cargo works as well. Do you have any list of work that needs to be done that maybe I could help with?

Just for argument’s sake, I think the answer to your first question is very clear: because it would enable more use cases. I personally never want to activate a virtualenv again in my life. It’s one of the worst parts of Python development. I never even want to be at risk of mutating my virtualenv in a way that isn’t tracked in a .toml or .lock file. So I want to make sure I use a tool that can take care of it entirely for me and isolate me from the environment.

However, the suggestion of having poetry actually run on python 2.7 would be a good alternative to supporting arguments like --two. So I’m happy as long as that’s eventually possible 😃