Pipeline
Pipeline is an asset packaging library for Django, providing both CSS and JavaScript concatenation and compression, built-in JavaScript template support, and optional data-URI image and font embedding.
Installation
To install it, simply:
pip install django-pipeline
Documentation
For documentation, usage, and examples, see : https://django-pipeline.readthedocs.org
History
1.6.8
Made templatetags easier to subclass for special rendering behavior. Thanks to Christian Hammond.
Updated the link to readthedocs. Thanks to Corey Farwell.
Fixed some log messages to correctly refer to the new PIPELINE settings tructure. Thanks to Alvin Mites.
Changed file outdated checks to use os.path methods directly, avoiding potential SuspiciousFileOperation errors which could appear with some django storage configurations.
1.6.7
Add a view for collecting static files before serving them. This behaves like django’s built-in static view and allows running the collector for images, fonts, and other static files that do not need to be compiled. Thanks to Christian Hammond.
Update documentation for the ES6Compiler to clarify filename requirements. Thanks to Nathan Cox.
Add error output for compiler errors within the browser. This provides for a much better experience when compiling files from the devserver. Thanks to Christian Hammond.
Make unit tests run against Django 1.6 and 1.7. Thanks to Sławek Ehlert.
1.6.6
Fix filtering-out of files which require a finder to locate.
Allow compilers to override the output path.
Fix error reporting when a compiler fails to execute.
Fix IOErrors when running collectstatic with some nodejs-based compilers and compressors. Thanks to Frankie Dintino.
Fix compatibility of unit tests when running on Windows. Thanks to Frankie Dintino.
Add unit tests for compilers and compressors. Thanks to Frankie Dintino.
1.6.5
Fix Django < 1.8 compatibility. Thanks to David Trowbridge.
Allow to disable collector during development. Thanks to Leonardo Orozco.
1.6.4
Fix compressor subprocess calls.
1.6.3
Fix compressor command flattening.
1.6.2
Remove subprocess32 usage since it breaks universal support.
1.6.1
Fix path quoting issues. Thanks to Chad Miller.
Use subprocess32 package when possible.
Documentation fixes. Thanks to Sławek Ehlert and Jannis Leidel.
1.6.0
Add full support for Django 1.9.
Drop support for Django 1.7.
Drop support for Python 2.6.
BACKWARD INCOMPATIBLE : Change configuration settings.
Metadata
Release files for django-pipeline-no-future 1.6.8.3
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-pipeline-no-future-1.6.8.3.tar.gz | 52.2 kB | Without provenance | Details |
Release files / django-pipeline-no-future-1.6.8.3.tar.gz
| Download URL | django-pipeline-no-future-1.6.8.3.tar.gz |
|---|---|
| Size | 52.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3be87bfb651d715598be388c2fb2203e28a64d47f2d0fbda5e743e3c59be7be0
|
|
BLAKE2b-256 checksum How to use checksums |
0b3d43c80ee8756b6b384c92576a3c11b41d660af43593c33126ed30a09fc449
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-pipeline-no-future 1.6.8.3
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.