This package provides a caching mechanism for Zope applications.
CHANGES
3.7.0 (2009-07-25)
Use the RAM cache implementation from zope.ramcache.
3.6.0 (2009-05-27)
Use zope.componentvocabulary instead of zope.app.component.
3.5.0 (2009-01-31)
Use zope.container instead of zope.app.container.
3.4.1 (2008-07-30)
Remove find-links from buildout.cfg.
Get rid of zope.app.zapi as a dependency. See http://launchpad.net/bugs/219302
Fixed deprecation warning in zope.app.cache.browser.cacheable: zope.app.i18n became zope.i18nmessageid.
3.4.0 (2007-10-11)
Initial release independent of the main Zope tree.
Metadata
Release files for zope.app.cache 3.7.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 | Actions |
|---|---|---|---|---|
| zope.app.cache-3.7.0.zip | 20.3 kB | Without provenance | Details for zope.app.cache-3.7.0.zip |
Release files / zope.app.cache-3.7.0.zip
| Download URL | zope.app.cache-3.7.0.zip |
|---|---|
| Size | 20.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e04aab53d9be6898253a69a2ac75ebb356a84e457744ed70e7641385a9c5a75
|
|
BLAKE2b-256 checksum How to use checksums |
b1909055931a4c6bc78f56d1edc8563c5889a600aa63cbde37283fe280fb487d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zope.app.cache 3.7.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.
