-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot import name create_environment with virtualenv >= 20 #2093
Comments
Not easily, how would you recommend I do that? |
@cjw296 I don't understand how you end up with |
@sdispater I'm also a user of CircleCI and seeing the same issue. CircleCI appear to pre-install poetry on their image, but have also upgraded the system |
Here's the relevant bit of their Dockerfile: |
I wonder where pip is coming from and what version it is? Maybe @FelicianoTech can help with this? |
Where do we find the docker file for the upstream Python image? |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).Poetry version: 1.0.3
pyproject.toml file: https://github.com/cjw296/carly/blob/master/pyproject.toml
Issue
virtualenv 20 was released earlier this month, and looks like CircleCI's images were just rebuilt to use it. So, now, on Python 2,
poetry install
fails as follows:The most pragmatic solution, at this point, is to have poetry pin the virtualenv it uses to
<20
, or just vendor it, since realistically, it's only going to be used on Python 2, right?The text was updated successfully, but these errors were encountered: