-
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
Support HTTP authentication for git dependencies #2050
Comments
Poetry is a really cool project. This is my first issue using it - so all thumbs up :). I'm not sure this should be a feature request. Stumbled across this trying to migrate a project from requirements.txt to poetry. Pip installed the git url with http basic authentication. Poetry failed when trying to add the same url:
Ok, maybe basic auth urls are just not supported. But trying this without username and password poetry ran into an endless dependency resolving loop:
I think this should be a bug report. |
Thanks a lot, I suspected something like that and therefore preserved the „+“ :). |
@evgenii-petrov-arrival I second this feature request, however this might be solved with #5581. Not 100% sure though |
HTTP Authentication is already supported in Poetry. See #5567 #5581. Doc: https://python-poetry.org/docs/dependency-specification/#git-dependencies |
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. |
Feature Request
I want to pull a dependency from a private git repo, but the repo requires HTTP authentication.
As far as I can tell, https://python-poetry.org/docs/repositories/ only supports PyPI repositories, so git repositories are not supported.
I want to be able to do something similar to:
Or, even better, to configure auth for the whole
git.domain
.Please add a way to specify a username and a password to be used when pulling a git dependency, such that the username and password are specified outside of pyproject.toml .
The text was updated successfully, but these errors were encountered: