-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Closed
Labels
C: cliCommand line interface related things (optparse, option grouping etc)Command line interface related things (optparse, option grouping etc)auto-lockedOutdated issues that have been locked by automationOutdated issues that have been locked by automationstate: awaiting PRFeature discussed, PR is neededFeature discussed, PR is neededtype: enhancementImprovements to functionalityImprovements to functionality
Description
What's the problem this feature will solve?
As described in #6720 (comment), pip may be using several sources of information for the CA certificate bundle to use for HTTPS requests. This makes it hard to debug user issues.
Describe the solution you'd like
In the output of pip debug we should include:
- the
certsetting from the highest-priority pip configuration file (and the configuration file path) - on second thought the location doesn't matter much os.environ.get('REQUESTS_CA_BUNDLE')os.environ.get('CURL_CA_BUNDLE')pip._vendor.certifi.where()
This will provide insight into the CA certificate bundle in use for a given request, which can then be used in instructions to the user in conjunction with curl/openssl to submit an HTTP request independent of pip and rule out pip-specific issues.
Alternative Solutions
Do nothing.
Additional context
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C: cliCommand line interface related things (optparse, option grouping etc)Command line interface related things (optparse, option grouping etc)auto-lockedOutdated issues that have been locked by automationOutdated issues that have been locked by automationstate: awaiting PRFeature discussed, PR is neededFeature discussed, PR is neededtype: enhancementImprovements to functionalityImprovements to functionality