collective.complexrecordsproxy
Providing a proxy class for plone.registry allowing IObject fields to be stored as separate records using the plone.registry collection support.
Motivation
With z3c.form it is possible to create forms allowing users to create and edit lists of complex records.
An example:
TODO from here.
We have a main interface with an object field etc.
We build a hierarchic structure composed of native types. All boils down to simple native types in the end, and so in theory is possible to store in the registry without violating this principle of plone.registry:
“To avoid potentially breaking the registry with persistent references to symbols that may go away, we purposefully limit the number of fields supported.
Usage
Changelog
1.1 (2022-01-13)
Add Python 3 & Plone 5.2 / 6.0 compatibility [boulch, laulaz]
1.0 (2016-01-29)
Initial release [sunew, tomgross]
Metadata
Release files for collective.complexrecordsproxy 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 |
|---|---|---|---|---|
| collective.complexrecordsproxy-1.1.tar.gz | 8.5 kB | Without provenance | Details for collective.complexrecordsproxy-1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective.complexrecordsproxy-1.1-py3-none-any.whl | Python 3 | none | any | Details for collective.complexrecordsproxy-1.1-py3-none-any.whl |
Total release size: 12.6 kB
Release files / collective.complexrecordsproxy-1.1.tar.gz
| Download URL | collective.complexrecordsproxy-1.1.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2db0f976edc10721f52352a57992f4f7561f65729ff41bcb6df914f028da453f
|
|
BLAKE2b-256 checksum How to use checksums |
906f38b5aab6c5744af5ede790e455d6271a20c7b580b42e283841c04110cc8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.0
|
Release files / collective.complexrecordsproxy-1.1-py3-none-any.whl
| Download URL | collective.complexrecordsproxy-1.1-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d2739f74243a1d7626c95bdff2225868c042c918d7e74250733939bad6fef04
|
|
BLAKE2b-256 checksum How to use checksums |
16b51dac77f322d187ee744f23f56aa673218bd6419e90b9755c7f7d9694f3d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.0
|
Security for collective.complexrecordsproxy 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.