proxy environment variable integration breaks other applications

[mcandre]

Description

pip proxy environment variables break curl, wget, and other common networking applications. Whereas other applications infer the scheme automatically and reject explicit schemes, pip requires them.

The specific pip --proxy CLI flag used at runtime also fails to override http_proxy, https_proxy environment variable configuration.

All of this adds unnecessary complexity to writing shell scripts for provisioning Python projects.

Can we please implement proxy scheme inference in pip and then phase out explicit schemes in these environment variables, in order to integrate more smoothly with other common networking apps?

Meanwhile, it would be useful to temporarily change pip's environment variable names from http[s]_proxy to PIP_HTTP[S]_PROXY, as a fast route to integration. Once the value conflict is resolved, we can readopt the industry standard names.

Expected behavior

pip proxy environment variable settings should not break curl.

pip version

20

Python version

3

OS

RHEL

How to Reproduce

Configure http_proxy according to curl/wget standards.

Try to install packages with pip.

Output

No response

Code of Conduct

• [X] I agree to follow the PSF Code of Conduct.