Backport of Django staticfiles storages from Django 1.7+ to earlier Django 1.6
Overview
Quick and dirty backport of the latest staticfiles storages from the latest Django to be used with Django 1.6. Tests are backported as well to ensure everything works, but butchered to remove post-Django 1.6 tests.
Requirements
Requires Django 1.6+ and as such Python 2.6+ as well
Installation
Simply use pip to install:
$ pip install django-future-staticfiles
Usage
The storages should be drop in replacements, so they can be used in settings.py for STATICFILES_STORAGE:
$ STATICFILES_STORAGE='django_future_staticfiles.storage.CachedStaticFilesStorage'
Contributing
Contributions are welcome, just create a pull request or issue on the GitHub repository for the project.
Metadata
Release files for django-future-staticfiles 0.1.0
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 | |
|---|---|---|---|---|
| django-future-staticfiles-0.1.0.tar.gz | 15.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_future_staticfiles-0.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 34.7 kB
Release files / django-future-staticfiles-0.1.0.tar.gz
| Download URL | django-future-staticfiles-0.1.0.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6385859b5782ebb7b70702c15f4a468c716d4f6e295d0e91dbf4a062719ba0d4
|
|
BLAKE2b-256 checksum How to use checksums |
a5d1e6d68d57324e3f4d517f98ecc91f34d623e3571f7f896eb23d81a7b91b15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_future_staticfiles-0.1.0-py2.py3-none-any.whl
| Download URL | django_future_staticfiles-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 19.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
460a91273f727271b04cd767859a0bb54bd4f595bd8bfba0eb6c0579f9d9e801
|
|
BLAKE2b-256 checksum How to use checksums |
f45c1f062d46b0177fb2d856b257d6c5e9fe5bb4a32a2a8a535253c1302664df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-future-staticfiles 0.1.0
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.