-
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 1.3.1 Pypi Certs #7513
Comments
maybe a result of running pip subprocesses with You seem to have figured out a solution so it's hard to get excited either way. |
Did this change between 1.2.1 and 1.3.1? |
Looks like it was changed with 1.3.0 |
This is intentional, if you need to coerce pip's behavior use the global pip configuration as per #3249. |
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. |
Poetry version: 1.3.1
Python version: 3.8.13
OS version and name: macOS 13.2
pyproject.toml
I have searched the issues of this repo and believe that this is not a duplicate.
I have consulted the FAQ and blog for any relevant entries or release notes.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option) and have included the output below.Issue
Hi Poetry team,
I wanted to report an issue that we are experiencing with installing dependencies in poetry version 1.3.1. Our org uses self signed certs, and we ran into an issue of not being able to reach Pypi https://pypi.org/simple/pip/ when installing dependencies. Is this expected behavior?
The solution we've come up with is to concat
certifi
certs into our private certs for poetry 1.3.1.We did not notice this issue with poetry 1.2.2, so wondering if anyone knows what cert logic has changed between 1.2.2 and 1.3.1.
Running poetry install
The text was updated successfully, but these errors were encountered: