microsoftgraph / microsoftgraph/msgraph-sdk-python
httpx python library issues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 630
- Forks
- 96
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
I work on the azure ansible collection and I've been trying to resolve a no_proxy bug in httpx library since January of this year and it has gone nowhere. Ansible's python libraries rely on kiota and msgraph libraries which both use httpx.
I put forward a pr to fix this here https://github.com/encode/httpx/pull/3741 But this has been ignored by the main developer. Now comments and discussions are turned off for the entire project.
I'm not the only one who noticed this and the project has been forked https://tildeweb.nl/~michiel/httpxyz.html
I would like to start a discussion on what to do next.
Thanks,
Bill
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 reviewing the reported no_proxy problem in httpx and the proposed fix in https://github.com/encode/httpx/pull/3741, then consider its impact on the kiota and msgraph libraries used by the Azure Ansible collection. The issue does not define a change or test target; its stated goal is to decide what to do next, with the httpxyz fork as additional context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100