pipx creates isolated application environments, but package retrieval still starts from the environment given to pipx. In a POSIX shell, a pip-backed installation can use:

http_proxy='http://proxy.example:8080' https_proxy='http://proxy.example:8080' pipx install --backend pip black

The assignments apply to this invocation and its child installer. They do not require putting the proxy URL into every created virtual environment. The HTTP proxy list offers endpoint candidates when these package downloads may use public intermediaries.

Current pipx exposes a backend choice. The explicit pip backend above makes the downloader clear. A pipx version predating that option may already use pip by default; use the syntax supported by the installed version.

pip itself also supports a --proxy option. If using pipx’s --pip-args to pass installer options, keep those arguments with the pip backend; they are not universal settings for another backend or for the installed command.

A successful installation does not configure black or any other installed application’s future network traffic. Launch a networked application with the environment or client settings that application supports. Conversely, setting a proxy only inside that application cannot repair the earlier package download.

For a certificate error, inspect the downloader’s trust configuration rather than disabling checks. A 407 concerns the intermediary’s account; a private-index login concerns the package source.

འབྲེལ་བའི་རྩོམ་ཡིག