This release is a pre-release and may not be stable for production use.
Overview
Experimental performance improvements to content creation for Plone.
Changelog
1.0rc1 - 2009-05-20
Package metadata and code cleanup. [hannosch]
Merged changes for archetypes new style factory compatibility. [hannosch]
Handle case of egg contained types if no product is set on fti at getDefaultAddableTypes. [rnix]
Switched __getitem__ to __getattr__ in FauxArchetypeTool. This makes it look up attributes on the real tool, which makes acquisition work again. [tesdal]
Added _setObject method from OFS, don’t fire events by default. [tesdal]
Initial package structure. [zopeskel]
1 maintainer
Metadata
1 maintainer
Release files for experimental.contentcreation 1.0rc1
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 |
|---|---|---|---|---|
| experimental.contentcreation-1.0rc1.zip | 19.7 kB | Without provenance | Details for experimental.contentcreation-1.0rc1.zip |
Release files / experimental.contentcreation-1.0rc1.zip
| Download URL | experimental.contentcreation-1.0rc1.zip |
|---|---|
| Size | 19.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbd77af84a3e9bfd5abb2ee798a5dfb2695964816167f37a75647968917f62c8
|
|
BLAKE2b-256 checksum How to use checksums |
d492e4065ea321ad7263125dc34a3e3077680c85f6c27df0570edb5cf8be0aff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for experimental.contentcreation 1.0rc1
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.
