-
Notifications
You must be signed in to change notification settings - Fork 963
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
Support PIP_INDEX_URL
for setting pip
index urls
#1535
Comments
PIP_INDEX_URL
and PIP_TRUSTED_HOST
for setting pip index urlsPIP_INDEX_URL
and PIP_TRUSTED_HOST
for setting pip
index urls
Also seeing 405s for a private PIP repo, probably worse a separate issue once I figure out more. |
We support See #1339 for discussion around trusted host support. |
+1! This is kinda smart. UV_* env cars should take precedence, but being able to understand PIP_* vars could drive adoption. For example: a client I work with has to inject PIP_INDEX_URL as a Docker build arg. If I wanted to use UV in my images, I'd have to open a PR with the devops team just for that. Tough luck. |
Also +1 in general if the idea is to be a drop-in replacement for |
I've considered it some more and basically I don't see a problem supporting these where it's not too invasive. Ideally we'd support I'd like to get consensus from other maintainers before work begins on this though. cc @charliermarsh |
PIP_INDEX_URL
and PIP_TRUSTED_HOST
for setting pip
index urlsPIP_INDEX_URL
for setting pip
index urls
Is
|
Yup -- I ran
|
Yes |
Yes it's exported and I tried echo,
(uv version is 0.1.14) |
Ahh no sorry it wasn't exported, it works now thanks! |
Hello, any update on this issue? It would be really helpful for uv adoption if uv could understand |
in export UV_DEFAULT_INDEX=$PIP_INDEX_URL |
Thanks @copdips I don't think we'll support reading pip variables — we support |
This is a request to support using alternative index urls - not just via the
--index-url
option - but also via the related pip environment variablesPIP_INDEX_URL
PIP_TRUSTED_HOST
(to support none https schemes)The use case I'm having is that I use a local pip server/proxy running on
http://127.0.0.1:<port>/...
. (This is to adhere to existing work policies/standards when usingpip
).The text was updated successfully, but these errors were encountered: