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
It seems pytorch broke something again, which broked poetry #6965
Comments
seems like a duplicate of #6939 and, as there, not a poetry bug. Take it to pytorch! |
It is not a direct duplicate of #6939 since I pointed down to the issue of torch directly. I see also a different problem here: Installing torch 1.13.0 directly with pip doesn't have any issue. This means the meta developer screwed it up and that might happen again. In the meantime for a dev it is ridiculous to figure out why the dependency of the package they wanted install rely on a dependency which has a new screwed up metafile version because it has a dependency which is not available on a specific platform. If I just add a new package that might be fine, but if this happen while update takes huge amount of investigation to recognize the issue. |
Poetry can't do anything about bad metadata from a package; you should pin to an old version of torch until this is resolved upstream. |
I know that poetry can't do anything about bad metadata from a package, but maybe we can turn this into a feature that if bad metadata from a package appears, the error message includes also information about the complete dependency tree. This would help to analyze the issue faster. We were only able to figure this out because the huge time investment sweeping through the |
Detecting "bad" (in this case, mismatched) metadata is its own challenge; we will not have a robust and performant way to do so until PEP 658 is implemented by indexes. At that point, yes, we can fail with a accurate, detailed, and descriptive error message when this happens. |
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. |
-vvv
option) and have included the output below.Issue
We noticed yesterday 03.11.22 that we could not install pytorch on a new system, because one dependency could not be satisfied. It was
nvidia-cudnn-cu11
. So I reproduced by following steps the setup and ended up with the same issue:which results always in the following error:
So we tinkered further and analyzed the
poetry.lock
and realized the dependencies fortorch=1.13.0
:Et voilá we found our troublemaker package. So we checked the metadata.files and realized:
only
manylinux
and nowin_amd64
like the others. So we were curious. What are the dependencies for version 1.12.1?and surprise:
the cuda dependencies are gone. We totally aware about that pytorch with cuda is a mess overall in poetry because:
But this problem appears also if pytorch-lightning or any other tool depends on pytorch and resolving such merge conflicts was absolutely catastrophic, since the newer version got autoresolved all the time...
The text was updated successfully, but these errors were encountered: