Skip to content
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

Install dependencies from private repository based on global configuration #4817

Closed
2 tasks done
JaviFuentes94 opened this issue Nov 23, 2021 · 4 comments
Closed
2 tasks done
Labels
status/duplicate Duplicate issues

Comments

@JaviFuentes94
Copy link

  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the documentation and believe that my question is not covered.

Feature Request

Hey poetry people!

In the process of migrating to poetry, we have found a blocker with relation to how extra indexes for downloading packages are handled.

The situation is that while in other tools you can just set PIP_EXTRA_INDEX_URL env variable with your private registry and you are set everywhere, poetry enforces you to add this index URL in every single project through the pyproject.toml file. This means that when an organization changes the registry the link to this registry needs to be updated in every single repository manually. This doesn't sound like a good design to me.

Given that the possibility to add repositories for publishing globally already exists, would it be possible to do the same for downloading packages? In my opinion, it is confusing that that feature only works for publishing but not downloading.

Looking forward to hearing your thoughts.

@JaviFuentes94 JaviFuentes94 added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Nov 23, 2021
@geudrik
Copy link

geudrik commented Dec 22, 2021

We just ran into this as well.. unless we're missing something too, this is kind of a big deal for us before we can really pull the trigger on poetry :S

@geudrik
Copy link

geudrik commented Dec 22, 2021

This means that when an organization changes the registry the link to this registry needs to be updated in every single repository manually.

This also means that users of scaffolding you build have to constantly remember to add in extra lines (plus a couple more to handle TLS CA's) for every single project they make, on top of the few hundred projects that we make

Pls to global package indexes 😢

@neersighted
Copy link
Member

Tracked in #5958.

@neersighted neersighted closed this as not planned Won't fix, can't repro, duplicate, stale Oct 9, 2022
@neersighted neersighted added status/duplicate Duplicate issues and removed kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Oct 9, 2022
Copy link

github-actions bot commented Mar 1, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status/duplicate Duplicate issues
Projects
None yet
Development

No branches or pull requests

3 participants