Introduction
This package allows you to experiment with the Zope 2 publisher’s marshalling features, as described here:
collective.formtoy Installation
If you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can do this:
Add collective.formtoy to the list of eggs to install, e.g:
[instance] ... eggs = ... collective.formtoyRe-run buildout, e.g. with:
$ ./bin/buildout
Changelog
1.0.0 - (2012-04-06)
Clean up package [aclark]
0.2 - 07/13/2010
Fix up docs
0.1 - 07/13/2010
Initial release
Metadata
Release files for collective.formtoy 0.3.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 | |
|---|---|---|---|---|
| collective.formtoy-0.3.0.zip | 20.2 kB | Without provenance | Details |
Release files / collective.formtoy-0.3.0.zip
| Download URL | collective.formtoy-0.3.0.zip |
|---|---|
| Size | 20.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2dce2cf3e4d1c64d90f1eb58303fa60faf05437ff89a845aa68e1d010d8e0dd
|
|
BLAKE2b-256 checksum How to use checksums |
d67e7d9b0d197217f545b7209fb370a67efa5ae041cda0a058e930771b420ae1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.formtoy 0.3.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.