Right now credentials for index-url in the configuration are stored in the url itself. I propose to somehow support credentials directly (or explicitly) in the configuration for private PyPIs because of following reasons:
- Right now credentials are leaked on multiple places. With this configuration:
[global]
index-url = https://thisis:test@pypi.python.org/simple
[search]
index = https://thisis:test@pypi.python.org/pypi
pip install --help shows:
Package Index Options (including deprecated options):
-i, --index-url Base URL of Python Package Index (default https://thisis:test@pypi.python.org/simple). This should point to a repository compliant with PEP 503 (the simple repository API) or a local directory laid out in the same format.
pip search --help shows:
Search Options:
-i, --index Base URL of Python Package Index (default https://thisis:test@pypi.python.org/pypi)
- With more exotic characters in the password it's not possible to use credentials in url at all:
[global]
index-url = https://username:pass/@word@pypi.python.org/simple
[search]
index = https://username:pass/@word@pypi.python.org/pypi
- AFAIK NuGet, mvn and npm support explicit auth since it's a good practice.
Right now credentials for
index-urlin the configuration are stored in the url itself. I propose to somehow support credentials directly (or explicitly) in the configuration for private PyPIs because of following reasons:pip install --helpshows:pip search --helpshows: