-
Notifications
You must be signed in to change notification settings - Fork 1k
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
uv pip compile
: markupsafe==3.0.2 has no wheels with a matching Python implementation tag
#8922
Labels
bug
Something isn't working
Comments
My guess is that this is because 3.0.2 exists on both indexes, but on the Torch index, it only has a Python 3.13 manylinux wheel. Perhaps we aren't looking at PyPI once we find that it has the same version, but at lower priority? |
(It does look like a bug though, in that case.) |
charliermarsh
added a commit
that referenced
this issue
Nov 9, 2024
…n multiple indexes (#8961) ## Summary At time of writing, `markupsafe==3.0.2` exists on the PyTorch index, but there's only a single wheel: `MarkupSafe-3.0.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl` Meanwhile, there are a large number of wheels on PyPI for the same version. If the user is on Python 3.12, and we return the incompatible PyTorch wheel without considering the PyPI wheels, PubGrub will mark 3.0.2 as an incompatible version, even though there are compatible wheels on PyPI. Closes #8922.
Fixed in the next release. |
konstin
pushed a commit
that referenced
this issue
Nov 10, 2024
…n multiple indexes (#8961) ## Summary At time of writing, `markupsafe==3.0.2` exists on the PyTorch index, but there's only a single wheel: `MarkupSafe-3.0.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl` Meanwhile, there are a large number of wheels on PyPI for the same version. If the user is on Python 3.12, and we return the incompatible PyTorch wheel without considering the PyPI wheels, PubGrub will mark 3.0.2 as an incompatible version, even though there are compatible wheels on PyPI. Closes #8922.
Wow, thanks for the extremely quick response! 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm facing an issue when including pytorch cpu index url. This is despite me using the
unsafe-best-match
index strategy. However, it is successful if I also specify the default pypi index url first. I suspect this is a bug.#7553
I have seen this other issue mentioned similar error with another package. However, the suggestion to use
--python-platform
option doesn't work regardless what value I used.Below is the miminal code.
It works if pytorch cpu index url is not used.
But fails if pytorch cpu index url is used.
It works if I add the default pypi index url first.
However, it gives the same error if the default pypi index url is specified last.
pip-tools has no issue.
If I were to downgrade markupsafe==3.0.1, it works.
versions
verbose output
The text was updated successfully, but these errors were encountered: