Not working behind firewalls

[GadgetSteve]

As there is no command line options for --proxy or similar and the settings that pip uses are not picked up this tool will not work if you are behind a firewall that requires such settings.

[lepisma]

Thanks for the suggestion. I can add a --proxy thing, but can't say when. It might be a short thing and probably just needs an extra dict with each requests call. Not sure if anything else is needed though.

[goriy]

I use environment variables http_proxy and https_proxy. I set them either locally in bat-file or globally in system-wide properties. And it works fine for me.

Example for Windows (pipwin_run.bat file):

set http_proxy=http://127.0.0.1:8080
set https_proxy=http://127.0.0.1:8080

pipwin %*

Replace 127.0.0.1:8080 to your proxy ip-address and port.

[anakaine]

I know this issue hasn't had any attention for a while - but I'd like to second this request. pipwin is invaluable in setting up some environments, but sometimes those environments need to be set up in the enterprise where proxies with usernames, passwords, and odd port choices exist.

Using the standard pip format for proxies would be good. --proxy=proxy.address:port

It's probably worth mentioning, also, that across a few organisations now I've not only had to use proxy, but also --trusted-host in order to get through the proxy.

[lepisma]

can someone do a PR here?