-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Source key word for Private repository #4920
Comments
Yes, please! I don't get how to query a private repository for only a few packages (and rely on PyPI by default for instance) @jules-ch did you find how to do it? |
Yes, you need to define your source & add it in the your package definition. [[tool.poetry.source]]
name = "gitlab"
url = "https://gitlab.com/api/v4/projects/<redacted>/packages/pypi/simple/"
secondary = true
[tool.poetry.dependencies]
python = ">=3.8,<3.9"
my_package_example = {version="0.1.0", source="gitlab"} |
yes, I finally found this, but I also found it does not work as I would expect. I have the same exact example than you, but when I do a => all packages (not only I would like basically to use one named "gitlab" to host 1 package and not trying to download every package on earth on it. Does not seem to work for now (at least with poetry 1.1.9) I even tried to use source = "pypi" to every package, still all request are done on both pypi and my private repo @jules-ch By the way, I just figured out that the doc is updated in the source code: https://github.com/python-poetry/poetry/blob/master/docs/dependency-specification.md#source-dependencies but not on website: https://python-poetry.org/docs/dependency-specification/ ... so basically, the issue you raised is already solved (but I still have my probable of secondary repositories being hit for every dependency) |
Documentation on |
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. |
Issue
There is no mention of the source keyword to specify a custom private repository for a specific package in the Dependency Specification section.
It should be added to provide information on how to specify a specific source for a package.
The text was updated successfully, but these errors were encountered: