This package defines interfaces of container components, and provides a basic container implementation. The available component is a generic and non-persistent ccontainer.
The package also provides some utilities to handle containers : an implementation of a zope.size.ISized component and an implementation of a zope.location.ISublocations component. They can both be registered as adapters, but cromlech.container doesn’t do it by default.
This package is the fruit of a fork from zope.container, in order to free it from the heavy zope dependencies and from the C module. Therefore, the behavior is different : the ContainedProxy component does not allow a transparent persistency.
Changelog
0.1 (2011-06-14)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for cromlech.container 0.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 |
|---|---|---|---|---|
| cromlech.container-0.1.tar.gz | 16.8 kB | Without provenance | Details for cromlech.container-0.1.tar.gz |
Release files / cromlech.container-0.1.tar.gz
| Download URL | cromlech.container-0.1.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f80ee3c3bbdcfb9712a62d9b0bb392b9589a2a8a66f7a7451115c90c4c55951e
|
|
BLAKE2b-256 checksum How to use checksums |
52d9c0311b4da3ba6445de81fd185fa7aff69dea27359296f5a356b08a790538
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cromlech.container 0.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.
