-
-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyoxidizer run fails behind proxy #15
Comments
Thank you for the valid bug report! I would have expected the Rust crate we're using ( Until I have time to fix this (hopefully in ~10 hours), you can work around the problem by downloading the archives referenced in the |
This is exactly what i did :-) |
This should be fixed in |
It feels like reqwest should at least have a helper for this. Did you open an issue? |
It seems like seanmonstar/reqwest#547 implements the feature in |
@indygreg
wget of this URL works:
|
Hello I'm hitting this problem behind corporate firewall.
A curl command on the url https://github.com/indygreg/python-build-standalone/releases/download/20211017/cpython-3.9.7-x86_64-unknown-linux-gnu-pgo-20211017T1616.tar.zst works as expected. It might be a regression. |
When running the getting started example the call to
pyoxidizer run
fails when downloading the python environment from behind a proxy. I am using windows cmd, the proxy settings are correctly set in the environment and working for e.g. cargo or wget:Is there a way, to set the proxy login info into the pyoxidizer.toml config file? So far i did not find any info on this..
The text was updated successfully, but these errors were encountered: