CodeVetter · Repo Unpack · System map
pallets/werkzeug
The main runtime boundary is the WSGI application callable, with separate adapters for request input and response output. Routing and HTTP utilities can operate independently of an application framework. Durable storage and rendering integrations are selected by consuming applications, as illustrated by the Redis-backed Shortly example. Packaging, CI, and documentation are configured through Flit, uv/tox, GitHub Actions, and Sphinx.
- The package-level API re-exports run_simple, Client, Request, and Response; README demonstrates a Request.application-decorated callable served by run_simple.
- Version 3.2.0.dev requires Python >=3.11 and MarkupSafe >=3.0.3; watchdog >=6 is an optional extra.
- Sans-I/O Request represents method, URL, and headers; the WSGI Request constructor derives those values from environ and retains the original environment.
- Map owns the state-machine matcher, endpoint-indexed rules, converter registry, and remapping lock; MapAdapter.match translates matcher outcomes into HTTP routing exceptions.
- Request-local resources include cached body bytes and parsed upload streams; Local separately stores context-scoped dictionaries in ContextVar.
- Shortly supplies its own Redis client, autoescaping Jinja environment, and route map; Redis keys hold URL targets, reverse mappings, identifiers, and click counts.
- Flit builds the package, while tox uses a uv lock runner to build a wheel and invoke pytest; dedicated tox environments run mypy, pre-commit, and Sphinx.
- Tag pushes trigger uv build, artifact upload, draft GitHub release creation, and PyPI publication using an id-token-enabled publish environment; deployment docs direct applications to dedicated production WSGI servers.