-
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
poetry export produces unresolvable requirements.txt #5407
Comments
Hello @Mchristos, please add your Thanks! fin swimmer |
Apologies, thought I had linked the pyproject gist. Both pyproject and lockfile are linked now: https://gist.github.com/Mchristos/83b524d022be9bc561b75e68d39d7305 https://gist.github.com/Mchristos/62eea04e582790616f634ed3e48f5fb6 |
Your lockfile says:
which is to say that poetry does not think that torchvision 0.12.0 depends on any particular version of torch, contrary to what pip says. https://pypi.org/pypi/torchvision/0.12.0/json agrees with poetry, whereas the METADATA in the torchvision .whl agrees with pip. Suggest raise an issue against torchvision asking them to publish consistent information to pypi. |
Great, thanks for looking into it and giving feedback. Appreciate it! |
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).OS version and name: Ubuntu 20.04 (WSL)
Poetry version: 1.1.13
Link of a Gist with the contents of your pyproject.toml file:
pyproject.toml
poetry.lock
Issue
Doing
poetry export -f requirements.txt
and installing dependencies in a fresh virtual environment from the resulting requirements, creates a situation where pip is unable to resolve the dependencies, due to conflicting version requirements among packages.Specifically, I am doing the following (inside a docker build, I should add)
This yields the following ResolutionImpossible error from pip:
The text was updated successfully, but these errors were encountered: