-
Notifications
You must be signed in to change notification settings - Fork 679
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
does not add extra-index-url
to the generated output file
#1502
Comments
Can you try passing |
Yes, that works. It will add the default I guess this could be the default behavior? |
I thought it wasn't the default in |
(Also, for whatever reason, I hid this in the CLI.) |
There are two more related issues here unsupported environment variables
generates
|
Furthermore, it doesn't use/manage |
You can use |
Hello @zanieb Thanks for your answer. I've just tried adding
|
The same here :( |
@nsphung -- Is |
@charliermarsh -- |
@hofrob The answer is No. |
@thomasaarholt -- Unrelated to this issue, but heads up: if you're using Gemfury, you need to use |
@thomasaarholt - I filed your other issue here, thanks! #2035 |
For clarity, this issue is now focused on whether we want to change our defaults around emitting index URLs. |
On this, maybe a source of confusion come from what is a pip index we should write. By defaut pip-compile write all specified indexes, but not the default one. When we activate the option, all pip indexes are written including the default one. And then if we activate this option by default (We should IMHO) we may want to create a new issue to only write specified indexes. |
@charliermarsh hello! is there any update / plan for fixing this one ? #1502 (comment) it's the main blocker for me ( and my team ) to replace our current slow workflow with a huge speed up from uv 😢 |
@iflare3g if you call |
@iflare3g - are you referring to the index URL emission issue, or that a package isn’t being found in an alternate registry? |
Second one, package isn't being found in private registry. |
i am successfully downloading and installing private packages using uv. Charlie's tip on the updated gemfury address fixed it for me. What is your full command (hiding any sensitive token), @iflare3g ? |
With
without the env var, the command is:
and the result is for both:
We use Microsoft's DevOps Artifacts for mirroring PyPI |
The only thing that knowingly doesn't work is if you have a package that exists both in your private registry and on PyPI (i.e., packages with the same name), and you expect to use a version of that package from PyPI instead of your private registry. Is that the case here? Does |
yup, only into private registry |
I'm waiting for this to be fixed as well. Else the resolution with index-url + extra-index-url is not working with |
me 2, it's the only thing that blocks me and my team to fully switch to uv and we'd like to do as soon as this will be fixed and released |
@iflare3g, I am successfully using
Or with a requirements.in, I would call
Ensure that you have updated uv in the venv you are using. |
Already tried with the latest one, otherwise I'd would have commented here the resolution for me. If more details are needed, I can share the verbose compile command result |
I think it would help if you shared the exact command you are running except for any secrets, and if you stick the verbose compilation log in a gist and share that too, I'm sure that would be helpful. Edit: Sorry, I see you shared it above! |
## Summary I don't know why I hid these in the first place. Maybe I copied these over from the `compat.rs` version. Closes #1502.
I think #1143 was only about parsing it from an existing input file. Running
pip-compile
will add this flag (and probably others) to the generated output.While testing
uv
, I haven't found out how to do this or if it's just missing.uv
Generates:
pip-compile
Generates:
Adding
--extra-index-url ...
to the requirements file would allow one to runuv pip sync requirements.txt
without having to add the cli argument.The text was updated successfully, but these errors were encountered: