Zope 3 Checkout Recipe

Recipe for creating a Zope 3 checkout in a buildout.

Hopefully, when Zope is packaged as eggs, this won’t be necessary.

The recipe has two options:

url

The Subversion URL to use to checkout Zope. For example, to get the 3.3 branch, use:

url = svn://svn.zope.org/repos/main/branches/3.3

This option is required.

revision

The revision to check out. This is optional and defaults to “HEAD”.

The checkout is installed into a subdirectory of the buildout parts directory whose name is the part name used for the recipe.

This location is recorded in a ‘location’ option within the section that other recipes can query to get the location.

Change History

1.2 (2007-02-09)

Added support for the buildout newest mode (-N option) to avoid checking for updates when -N is used.

1.1 (2007-01-22)

Feature Changes

Added an update method to work well with current buildout versions.

Bugs Fixed

When updating installs, extensions and package-includes weren’t updated properly.

1.0.dev_r68900

Initial release.

Download

Metadata

Release files for zc.recipe.zope3checkout 1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for zc.recipe.zope3checkout 1.2
File	Interpreter	ABI	Platform	Actions Reset
zc.recipe.zope3checkout-1.2-py2.4.egg 5.6 kB Feb 9, 2007 Without provenance	Legacy Egg format	-	-	Details for zc.recipe.zope3checkout-1.2-py2.4.egg

Release files / zc.recipe.zope3checkout-1.2-py2.4.egg

Download URL	zc.recipe.zope3checkout-1.2-py2.4.egg
Size	5.6 kB
Tags	Egg
SHA-256 checksum How to use checksums	`c942158ea55c1baea9a197ad1e7efeb51d8d98ab8c6fdd2f5b437501ce444df5`
BLAKE2b-256 checksum How to use checksums	`877310d24320f06834ffe3d47fd1edc038a33c742b3850747682ff602f59ac34`
Upload date	Feb 9, 2007
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for zc.recipe.zope3checkout 1.2

Report project as malware

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.