-
Notifications
You must be signed in to change notification settings - Fork 1.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 install failes for wheel URLs with placeholder #8082
Comments
My initial reaction is that it seems correct to fail here (I'm somewhat surprised this recommend this), and pip's lack of enforcement seems more like a bug than a feature. |
I think I agree. I hadn't seen this pattern before. |
It violates the Python packaging specs (the binary distribution spec requires the version to be in the wheel name), so i consider this a bug in their packaging system - Thanks for filing the upstream bug! |
I just ran into the same issue with the same package. Are you guys thinking of adding a flag to circumvent this, or should I try to push for them to change their practice? FWIW I don't think it's a bug as in unintended on their part, but an "easy" way to let people install the latest nightly version without having to update the url accordingly? |
This can be done by using a |
Roger that, will turn to the vllm repo then |
A few of us from the vLLM project are addressing this issue so that you can use |
Running into this with the huggingface.co/docs/bitsandbytes package as well. The wheel it fails with: |
I believe this has been (or is being) fixed with vLLM specifically, but in general I think this is the correct behavior for uv. For bits-and-bytes, it seems like they should be including the local tag in the wheel filename... Though we can make it optional. |
+1 Same problem here with |
I was following the
vllm
nightly installation guide where they have this one-liner for installing their nightly wheels:Their documentation specifically says:
when using
uv pip install
I get:but doing vanilla
pip install
works.The text was updated successfully, but these errors were encountered: