wheezy.routing
wheezy.routing is a python package written in pure Python code. It is a simple mapping between URL patterns (as plain simple strings, curly expressions or regular expressions) to a handler that can be anything you like (there is no limitation or prescription what handler is or could be).
The mapping can include other mappings and constructed dynamically.
It is optimized for performance, well tested and documented.
Resources:
- source code, examples and issues tracker are available on github
- documentation
Install
wheezy.routing requires python version 3.10+. It is independent of operating system. You can install it from pypi:
pip install -U wheezy.routing
If you run into any issue or have comments, go ahead and add on github.
1 maintainer
Metadata
1 maintainer
Release files for wheezy.routing 3.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wheezy_routing-3.2.2.tar.gz | 10.7 kB | Without provenance | Details |
Release files / wheezy_routing-3.2.2.tar.gz
| Download URL | wheezy_routing-3.2.2.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6deef0159303caa04a6f8cd140ffe973f377cf17aebfbf9a79e20a431b363110
|
|
BLAKE2b-256 checksum How to use checksums |
c3be7bcdf4701b40f5edca6c83dda8f4d52eccffe83bea9ea81979fff61dbda5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for wheezy.routing 3.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
