Fix handling errors 401, 403 when looking for repositories

[cereblanco]

Pull Request Check List

fixes error handling related to: #3303

• Added tests for changed code.
• Updated documentation for changed code.

[MeanderingCode]

My experience of our pypicloud returning an HTTP 401 is that requests raises an HTTPError, meaning that I believe your response status code should go in the except HTTPError block.

But that aside, this does not fix the authentication problems some (myself included) are finding with, for example, a pypicloud serving private packages directly with HTTP Basic auth or via authenticated AWS S3 URLs.

See #3041

Perhaps proper error handling, as this addresses, is separate, but I wanted to ensure you had more context.

EDIT: Read more code and realized authentication is not related to this.

[MeanderingCode]

Looks like the exception is raised manually, below your conditional, so I believe I spoke in error.

[jensgustafsson]

What's the status on this PR?

[abn]

Thank you for your contribution @cereblanco. This might require a rebase as well.

[kasteph]

Hi @cereblanco this PR still needs to be rebased because of the breaking CI build. Thank you in advance!

[erdemuysal]

Hi 🤚

How can I get information about when the new version with this change will be released?
We need this in our scenario.

[ogunoz]

@erdemuysal I faced the same issue. They approved the MR for poetry 1.2.0 release

Currently it is available only as an alpha release. It solved my problem.
You can update your poetry with either:
poetry self update --preview
or:
pip install https://github.com/python-poetry/poetry/releases/download/1.2.0a2/poetry-1.2.0a2-py3-none-any.whl

[judahrand]

Is there a reason not to back port this to 1.11? @stephsamson

[1ace]

@abn @sdispater Could this simple and non-intrusive fix be backported to 1.1.x please? Thank you 🙂

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.