Improvements to WhiteNoise:
Serve media as well as static files.
Save media with hashed filenames, so they can be cached forever by a CDN.
Do not crash the collectstatic management command when a referenced file is not found or has an unknown scheme.
Add django-pipeline integration.
Add support for Django 1.6 via monkey patching.
Strip the Vary header for static file responses via middleware, to work around an IE bug. This should come before SessionMiddleware in MIDDLEWARE_CLASSES. See: http://stackoverflow.com/a/23410136
1 maintainer
Metadata
1 maintainer
Release files for ixc-whitenoise 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ixc_whitenoise-0.6.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for ixc_whitenoise-0.6.1-py2.py3-none-any.whl |
Release files / ixc_whitenoise-0.6.1-py2.py3-none-any.whl
| Download URL | ixc_whitenoise-0.6.1-py2.py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
fff5aef604c2ebb52c3a838213a9a6be84dea137aed9d167163d183025fe85e3
|
|
BLAKE2b-256 checksum How to use checksums |
8302075fc0c3cc6916235ee2ee91ddaba64ebb15757685045e75523dc0e49aef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ixc-whitenoise 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.
