-
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
Poetry 2 POETRY_HTTP_BASIC_ issues #10085
Comments
As per https://python-poetry.org/docs/repositories/#configuring-credentials
And in step (5) seems the username is PS: I do not use Azure DevOps Pipeline. Also see https://github.com/NathanVaughn/poetry-azure-artifacts-plugin. |
@abn I suspected it might be that but was honestly too lazy to actually test it (since it was working without it before ...?). I set it to some dummy value and that seems to do the trick. ... thanks for your time! (I'm still curious if there was a change in Poetry 2 that explains why it worked previously but does no longer do so.) |
This change largely reverts the decision made in b544ed5 as it seems that it is commonplace, albeit not best practice, for private indices to require or document that users use an empty username. The change in behaviour seems to surprise users migrating from 1.x (python-poetry#10085).
The change was introduced in #9850 which was released in 2.0.0. See also #9850 (comment). I have also raised #10088 to revert most of that change and to allow empty usernames in the next release. But this is up for discussion. |
This change largely reverts the decision made in b544ed5 as it seems that it is commonplace, albeit not best practice, for private indices to require or document that users use an empty username. The change in behaviour seems to surprise users migrating from 1.x (python-poetry#10085).
Description
This is going to be a very bad bug report as I have little information to provide, sadly.
When I upgrade from 1.8.4 to 2.0.1 my pipeline fails to pull from a private registry. It's an Azure DevOps pipeline and I use the PipAuthenticate task and then export the password as POETRY_HTTP_BASIC_registry-name_PASSWORD.
I also provide the password via env locally and that works fine with Poetry 2. I am clueless to why it breaks the pipeline - perhaps someone has an idea.
Workarounds
none
Poetry Installation Method
pip
Operating System
some Ubuntu, I guess
Poetry Version
2.0.1
Poetry Configuration
the default, I guess - can print it out if it helps
Python Sysconfig
Example pyproject.toml
Poetry Runtime Logs
poetry-runtime.log
The text was updated successfully, but these errors were encountered: