This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
betahaus.pyracont README
This packages main goal is to provide:
Basic ZODB-based content type skeleton for Pyramid.
Dynamic content types that can be adapted to pretty much suit most purposes.
Ability to make highly pluggable components sutable for frameworks.
Easy integration with colander.
This package currently lacks proper documentation, but should be pretty stable regarding API changes since it’s used in production in other open source projects.
Possible TODOs:
Custom field adapters instead of custom field types. No point in storing persistent content types unless needed.
With field adapters content types don’t need special settings.
This might require an introspection tool, otherwise it might appear to “magical”.
A way to transform input before it’s saved.
0.3b - 2015-03-27
suggest_name method now handles non-ascii better. This changed the dependencies from ‘slugify’ to ‘awesome-slugify’.
0.2b - 2014-02-11
Possibility to bind zope interfaces to schemas so objectevents will work as expected. This enables subscribers for schemas.
Factory names can now be omitted - the class name is used in that case.
Python 3 should work now.
0.1a4 - 2012-09-05
New method to make sure new objects aren’t stored with the same name as an existing view. Before it was possible to name objects the same way as views. [robinharms]
0.1a3 - 2012-02-14
Typo on code caused description to be stored under the wrong attribute of the schema when using createSchema. [robinharms]
0.1a2 - 2012-02-14
If title and descriptions are specified for the schema factory, also transfer them to the schema itself. (Colander Schemas are transfered to Schema nodes on construction, which enables title and description) [sassur]
0.1a1 - 2011-10-14
Exception raised when custom accessors or mutators created a loop. [robinharms]
Exposing field_storage as a public attribute should remove the need to the switch to override custom accessors / mutators. So it has been removed. Hopefully this will make it easier to use. [robinharms]
0.1a
Initial version
Metadata
Release files for betahaus.pyracont 0.3b0
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 |
|---|---|---|---|---|
| betahaus.pyracont-0.3b0.tar.gz | 16.2 kB | Without provenance | Details for betahaus.pyracont-0.3b0.tar.gz |
Release files / betahaus.pyracont-0.3b0.tar.gz
| Download URL | betahaus.pyracont-0.3b0.tar.gz |
|---|---|
| Size | 16.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dad073aa83562b1cc0eb9f39d97bf7634b0863ae0ee62923e43fb66ecf8d09ae
|
|
BLAKE2b-256 checksum How to use checksums |
fb0f207ab7f4d69819d9c995bf7ba3fd37cd06fb4369d1d922bb55df0c7683a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for betahaus.pyracont 0.3b0
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.