HTTP_PROXY et al. Environment Vars Not Supported
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 603
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
Unlike requests, treq doesn't support the (semi-standard) environment variables for proxy configuration, such as HTTP_PROXY, https_proxy, no_proxy and others. This makes it unusable in some applications, such on company networks that do not allow direct Internet access.
This is a separate concern from issue #174 and corresponding PR #130: those appear to talk about/provide only programatic proxy support, which would still require users running third-party code that uses treq to change that third-party code if they must use a proxy. (That said, integrating PR #130 would still be helpful to me in some situations, so I'd still encourage integrating it ASAP.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing treq's HTTP request and proxy configuration paths, then compare the scope with issue #174 and PR #130. Done means treq recognizes HTTP_PROXY, HTTPS_PROXY, and no_proxy-style environment variables for proxy configuration, with behavior covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100