encode / httpx · Architecture

The analyzer recorded three top-level subsystem directories: docs, httpx, and tests. The analyzed inventory counts 124 files: 40 in tests, 36 in docs, 24 in httpx, 9 in scripts, 8 in .github, and 7 at the repository root.

The role records name package modules under httpx/, including __init__.py, _client.py, _models.py, _urls.py, _urlparse.py, _content.py, _utils.py, and _exceptions.py.

Platform metadata records Python as the primary language, with the topics asyncio, http, python, and trio. The repository's platform description reads 'A next generation HTTP client for Python.'

What the scripts/ and .github/ directories hold beyond their file counts is not established by this packet.

This packet contains no detected entrypoints and no bounded execution paths. The analyzer established no clear executable starting point for the repository. No clear entrypoint was detected by the v0.10 heuristics, so the runtime starting point is not established. With no bounded static execution path available, runtime flow must be treated as unresolved.

The packet therefore reports no terminal reasons, truncation points, or cycles for any path, and it cannot identify which module is reached first.

The nearest flow-shaped evidence is the static relation record set: 4564 relations in total, of which 4105 are calls and 459 are imports.

Roles here are inferred by the analyzer from static resolved call degree and entrypoint membership, not observed at runtime; they indicate structural connectivity, not proven importance.

• httpx/__init__.py is the most connected entry in the role list: 885 incoming, 0 outgoing, labeled a leaf/data-boundary candidate.
• httpx/_exceptions.py also shows only incoming traffic (49 incoming, 0 outgoing), labeled a leaf/data-boundary candidate.
• httpx/_models.py (33 incoming, 66 outgoing) and httpx/_client.py (12 incoming, 51 outgoing) are labeled service/core candidates.
• httpx/_content.py (24 in, 26 out), httpx/_urls.py (20 in, 14 out), httpx/_urlparse.py (18 in, 28 out), and httpx/_utils.py (39 in, 2 out) are each labeled service/core candidates.
• Test files appear in the same ranking: tests/client/test_auth.py (39 incoming, 127 outgoing) and tests/models/test_responses.py (31 incoming, 128 outgoing) are labeled service/core candidates.

The packet quantifies where static paths stop mainly through relation counts: of 4564 recorded relations, 3061 are external or unresolved and 1503 are local. The analyzer does not resolve reflection, runtime dependency injection, dynamic imports, monkey-patching, generated code, framework runtime wiring, or dynamic dispatch. Calls made through those constructs are expected to sit among the external-or-unresolved relations.

The unresolved total is not attributed to specific targets, so the split between external libraries and dynamic constructs is not established. Beyond the limitation list and the unresolved-relation total, the packet provides no named boundary records, so plugin loading or dispatch boundaries are not individually documented.

The dependency records list 14 entries from requirements.txt, each pinned to an exact version and each recorded with scope 'runtime': chardet, mkdocs, mkautodoc, mkdocs-material, build, twine, cryptography, mypy, pytest, ruff, trio, trio-typing, trustme, and uvicorn. These records come only from requirements-style manifests parsed by the analyzer; pyproject.toml dependency tables were not parsed.

Within the package, the resolved-relation sample shows httpx/_api.py importing symbols from httpx/_client.py, httpx/_config.py, httpx/_models.py, httpx/_types.py, and httpx/_urls.py, with its request and stream functions calling httpx/_client.py:Client. The verb functions get, options, head, post, put, patch, and delete each call httpx/_api.py:request. The sample also shows httpx/_auth.py importing from httpx/_exceptions.py, httpx/_models.py, and httpx/_utils.py, with BasicAuth._build_auth_header calling httpx/_utils.py:to_bytes.

These relation strings are a summary sample; the full record set counts 1503 local and 3061 external-or-unresolved relations.

The analysis is static only: reflection, runtime dependency injection, dynamic imports, monkey-patching, generated code, framework runtime wiring, and dynamic dispatch are not resolved. Runtime wiring and dynamic-import behavior are therefore invisible to this packet.

Install, run, and build inference is partial, and installation commands are not verified. Bounded analysis also caps coverage: files over 400 kB, minified bundles, and vendored directories are inventoried but not parsed, and relation extraction is capped at 2500 relations per file and 150000 per repository.

The manifest's capability notes describe the analyzer itself, not this repository. The summary counts 40 test-like files. How the project behaves at runtime, including what its tests exercise, remains unresolved because no bounded execution path is available.

The analyzer classifies README.md, pyproject.toml, requirements.txt, and LICENSE.md as project-level important files. Its learning-path guidance is to start with manifests and important symbols and to inspect unresolved boundaries before changing code.

One sequence grounded in the role records: begin at httpx/__init__.py (885 incoming calls), continue through httpx/_client.py and httpx/_models.py, then the support modules _urls.py, _urlparse.py, _content.py, and _utils.py, and finish in the tests subsystem.