Repository navigation
Contributor-facing "how the client is put together" page? #3806
Unanswered
CHAPIBUNNY
asked this question in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When reading the code I mapped how a request travels:
Client.send()→_send_handling_auth()(auth flow generator) →_send_handling_redirects()(event hooks, redirects) →_send_single_request()→ the transport (HTTPTransportover httpcore by default, orWSGITransport/ASGITransport/MockTransport).AsyncClientmirrors it. The models (Request,Response,Headers,Cookies) live in_models.py, URLs in_urls.py/_urlparse.py, bodies in_content.py/_multipart.py, and decoders in_decoders.py. The apparent import cycles between_models,_types,_exceptionsand_configareTYPE_CHECKING-only.Would a short page like that be useful in the docs (perhaps next to
docs/contributing.md)? If it's out of scope, no problem.Disclosure: I maintain RepoLens, a docs tool, and used it (v1.15.2) for the first map; I checked it against the source by hand.
Drafted with RepoLens, checked by hand.
All reactions