Deliverance does transformations of HTML to ‘theme’ pages, similar in function to XSLT but using a simpler XML-based language to express the transformation.
New in this version
Deliverance now discards caching headers from the request before fetching the theme resource, since it doesn’t know how to handle 304 responses internally. This prevents Deliverance from serving unthemed content if the client request contains caching headers that would cause the theme server to respond with 304 Not Modified.
Release files for Deliverance 0.6.1
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 | |
|---|---|---|---|---|
| Deliverance-0.6.1.tar.gz | 310.6 kB | Without provenance | Details |
Release files / Deliverance-0.6.1.tar.gz
| Download URL | Deliverance-0.6.1.tar.gz |
|---|---|
| Size | 310.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ac8bd8b9a3b21fa6745e69dafbfd436bbb96b6eb512102993c775dbd8fae1ba
|
|
BLAKE2b-256 checksum How to use checksums |
a05db6708e61e6f3dea0b564a9def981738bd079ac83e3035e3e331571976566
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Deliverance 0.6.1
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
