Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Environment support
See original GitHub issueNeeds to handle anything that requests currently deals with when trust_env=True is set.
.netrc, REQUEST_CA_BUNDLE and anything else relevant.
First step to dealing with this would be to outline exactly what set of stuff requests includes. If anyone wants to dig into this and comment on this issue comprehensively with what set of behavior we need, then that’d be a great start.
We have adapters/environment.py currently stubbed out to deal with adding in this behavior.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I did some research in the Requests docs looking for environment variables it supports, and whether we support them already:
NETRCREQUEST_CA_BUNDLEorCURL_CA_BUNDLE(see here and here).HTTP_PROXY,HTTPS_PROXY(see here),ALL_PROXY,NO_PROXY.(Note that the names of the
*_PROXYenvironment variables seems be a convention.)To make extra sure we don’t miss anything, it would probably be worth cloning the Requests repo and grepping our way using
environment variable,os.getenvandos.environ.get.The scope of this issue is rather broad, so if that’s confirmed and as suggested by @sethmlarson in https://github.com/encode/httpx/pull/277#issuecomment-525036637, how about creating issues for each set of environment variables?
If this is still important, I’d be interested in doing some research here to determine what exactly requests includes, and then possibly implementing proper functionality.