cone.zodb
This package provides ZODB integration in cone.app and basic application nodes for publishing ZODB models.
Changes
1.1.2 (2026-10-31)
Use MappingOrder instead of the deprecated Order behavior. [rnix]
Sort the imports with ruff (one per line, from imports first, no sections) and format the code with ruff format (90 characters per line, single quotes). [rnix]
Add import sorting (I rules) and the formatter settings to the ruff configuration in pyproject.toml. [rnix]
1.1.1 (2026-10-24)
Modernise the code ruff flags as outdated: u'' prefixes, class X(object). Behaviour unchanged. super(Class, self) is kept, see cone.app. [rnix]
Add qa.ruff domain to Makefile and pin the ruff rule selection in pyproject.toml, make check runs ruff check. [rnix]
Pin setuptools<82.0.0 in mx.ini. pyramid 2.0.2 still imports pkg_resources, which setuptools 82 removed. [rnix]
1.1.0 (2026-02-03)
Refactor package layout to use pyproject.toml and implicit namespace packages. [rnix]
Setup Makefile. [lenadax]
Run tests with pytest. [lenadax]
1.0 (2025-10-25)
Pin upper versions of dependencies. [rnix]
Setup Makefile. [lenadax]
Run tests with pytest. [lenadax]
1.0a3 (2022-10-06)
Replace deprecated use of IStorage by IMappingStorage. [rnix]
Replace deprecated use of Storage by MappingStorage. [rnix]
Replace deprecated use of Nodify by MappingNode. [rnix]
Replace deprecated use of NodeChildValidate by MappingConstraints. [rnix]
1.0a2 (2021-10-21)
Implement node.iterfaces.IOrder on ZODBEntry. [rnix]
1.0a1 (2020-07-09)
Fix case where _v_parent is not set if ZODBEntryNode is not read via ZODBEntryStorage but from ZODB root directly. [rnix]
Remove AsAttrAccess, Nodespaces, and Attributes behaviors from ZODBEntry. [rnix]
Add ZODBEntryStorage.attrs. Returns attributes of related ZODBEntryNode. [rnix]
Add ZODBEntryNode.__getitem__. Sets ZODBEntryNode.entry as parent on children to keep traversal and acquisition paths sane. [rnix]
Access principal_roles when initializing nodes with ZODBPrincipalACL behavior applied to avoid lazy creation. Needed to prevent _p_changed being set on first access. [rnix]
Do not remember principal_roles via instance_property decorator on ZODBEntryPrincipalACL to avoid ZODB.POSException.ConnectionStateError errors. [rnix]
Proper handling of ZODBEntry and ZODBEntryNode in zodb_path. [rnix]
Add include_entry attribute to CatalogAware behavior. Flag controls whether to index entry node in calatog. [rnix]
Add entry property to ZODBEntryNode. [rnix]
Use pyramid_zodbconn instead of repoze.zodbconn. [rnix]
Set node.interfaces.IOrdered on cone.zodb.entry.ZODBEntry to fix treerepr. [rnix]
Python 3 compatibility. [rnix]
Upgrade to cone.app 1.0b1. [rnix]
< 1.0
Initial work. [rnix]
License
Copyright (c) 2011-2021, BlueDynamics Alliance, Austria Copyright (c) 2021-2025, Cone Contributors All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1 maintainer
Metadata
1 maintainer
Release files for cone.zodb 1.1.2
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 |
|---|---|---|---|---|
| cone_zodb-1.1.2.tar.gz | 13.0 kB | Without provenance | Details for cone_zodb-1.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cone_zodb-1.1.2-py3-none-any.whl | Python 3 | none | any | Details for cone_zodb-1.1.2-py3-none-any.whl |
Total release size: 28.9 kB
Release files / cone_zodb-1.1.2.tar.gz
| Download URL | cone_zodb-1.1.2.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abc1b1b10df3b3d5d4b473888ac24d820caec90f2baaba67e157683022458f13
|
|
BLAKE2b-256 checksum How to use checksums |
046ce0a2fc46a12f62931d25cbf7e3e068fb6a724646cbff4baa09322d26e4fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Release files / cone_zodb-1.1.2-py3-none-any.whl
| Download URL | cone_zodb-1.1.2-py3-none-any.whl |
|---|---|
| Size | 15.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc63ab3b668d5b12cb2ae8adf5d0dcd865e8b0fa5347b1dc1c05f00a8db7e4c1
|
|
BLAKE2b-256 checksum How to use checksums |
2ef01e0b6f9fd20e0e2eb4d468daef34a7aa97fed7f3f5bf3ebb3d95e1868ec7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Security for cone.zodb 1.1.2
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.
