-
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
Possibly TLS related package installation problem #7202
Comments
I have this issue too. Poetry is installed via pip in a Docker image for our ci-cd.
Works fine on Python 3.9 with poetry 1.1.14, and 1.2.2. Some packages do install, but this one failed: (I will update this post with a -vvv asap)
|
possibly a duplicate of #7182 |
Indeed, poetry is not using the primary custom pypi, but use the official one instead. Which makes it fail. Thanks ! |
Looks likely for our case, too. Will try to reproduce tomorrow with blank proxy settings. |
Closing as duplicate, I think we should update the release announcement/blogpost with a heads up/explanation. Thanks for the list of paths @FlotterCodername. |
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. |
-vvv
option) and have included the output below.Issue
Some of my colleagues are reporting a package installation issue that happens with 1.3.1 but not with 1.2.2.
These users have installed poetry via pip. Personally, I have not been able to reproduce this, but will keep trying and also provide a
-vvv
output.PyPI in use are two different Artifactory PyPIs. The certificate PEM is in the root of the repository.
Our
poetry.toml
:Package installation output:
I believe this is TLS related -- when I generated the lockfile for the colleague and asked them to install it, the error below came up.
I asked them if they were in the root of the project directory, but then realized they were using the PyCharm GUI, so it should definitely be running there.
The text was updated successfully, but these errors were encountered: