Zope 2 Instance
This package provides a buildout recipe for creating a Zope 2 instance based around a deployment.
The deployment concept originates from zc.recipe.deployment and allows the deployment to control where resources of a particular type are created.
While zc.recipe.deployment is suited to production use, you will likely find that gocept.recipe.deploymentsandbox is more useful for development.
This recipe is only compatible with Zope 2.12+.
Metadata
Release files for zope2instance 1.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 |
|---|---|---|---|---|
| zope2instance-1.1.tar.gz | 10.9 kB | Without provenance | Details for zope2instance-1.1.tar.gz |
Release files / zope2instance-1.1.tar.gz
| Download URL | zope2instance-1.1.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3daff1a3056c8f7469d236c549b2889a82cc015ec648e2847195a2df9702ba67
|
|
BLAKE2b-256 checksum How to use checksums |
ac489edecbb36e93514b6c6aa5995fc17edf81a10829630f4b5c4ef1970c2f80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zope2instance 1.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.