silva.resourceinclude
silva.resourceinclude collect and merge resources files (CSS, KSS, JS) on layers. It was based on z3c.resourceinclude. It’s used by silva.core.layout to easily include resources in Silva themes for Silva 2.x. In Silva 3, silva.fanstatic replaces this extension.
It provides as well a full implementation of the Zope resource export mechanism for Zope 2, that properly implement HEAD requests and are optimized for caching purpose.
Please refer to the official Silva documentation to see how to use it.
Code repository
You can find the source code for this extension in Git: https://github.com/silvacms/silva.resourceinclude
Changes
2.2.1 (2010/12/20)
Prevent a bug with Grok if CHAMELEON_DEBUG is set.
Improve resources merging to prevent where some resources where not included in the merged version.
2.2 (2010-10-27)
Resource merging is now done when the server is starting. That prevent issues in case of multi Zope instance installation. Usefull logging is done to know what is merged and how.
Support for the directive only_for have been added. It is the equivalent of the context option used with ZCML directives.
2.1 (2010-10-07)
Bug fix on windows: fix merged resources to be able to properly access other relatives resources.
Bug fix on windows: fix mode used to open files in order to fully get all resource data out of them.
Vary cache key on HTTP_HOST for the resource include provider (that let you access the same site with different hostname and get URL for the hostname you asked in your response).
plone.memoize is replaced with silva.core.cache.
It is now to include a ressource only for a given content. The ZCML is extended with a context option that let you do that.
A new ZCML directive called resourceLayerInclude let you reinclude for a different layer and content a list of resources defined on an interface with the martian directive.
2.0 (2010/07/15)
Implement resources export, and use it,
Improve caching (HTTP headers, HEAD requests, 304),
Update syntax and imports for Zope 2.12 and Python 2.6.
1.0b2 (2009/12/09)
Refactor merged resources code.
Fix a thread safe issue.
Don’t depend anymore on z3c.resourceinclude.
Improve caching.
1.0b1 (2009/11/18)
Add the resource grokker.
Fix various bugs from the previous version.
1.0a1 (2008/11/17)
Initial release.
Metadata
Release files for silva.resourceinclude 2.2.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 | Actions |
|---|---|---|---|---|
| silva.resourceinclude-2.2.1.tar.gz | 20.2 kB | Without provenance | Details for silva.resourceinclude-2.2.1.tar.gz |
Release files / silva.resourceinclude-2.2.1.tar.gz
| Download URL | silva.resourceinclude-2.2.1.tar.gz |
|---|---|
| Size | 20.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4bddcf40f560fc56107207081d1d95604da104540f85091ad4936364b33a34fd
|
|
BLAKE2b-256 checksum How to use checksums |
041fdc8badc516f287881c9c9d55fe5302a4342fc6fbf71b9685a771b1203b15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for silva.resourceinclude 2.2.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.