node.ext.zodb 2.0.0

Node Implementation with ZODB persistence

node.ext.zodb

Overview

node.ext.zodb is a persistent node implementation for the ZODB.

For more information about node see https://pypi.python.org/pypi/node

Source Code

The sources are in a GIT DVCS with its main branches at github.

We’d be happy to see many forks and pull-requests to make it even better.

Python Versions

• Python 2.7, 3.7+

Contributors

• Robert Niederreiter (Author)

• Jens Klein

Changes

2.0.0 (2026-02-03)

• Refactor package layout to use pyproject.toml and implicit namespace packages. [rnix]

1.7 (2025-10-25)

• Pin upper versions of dependencies. [rnix]

1.6 (2022-12-05)

• Pass name and parent as keyword arguments all over the place. Preparation for use of NodeInit behavior instead of DefaultInit. [rnix]

1.5 (2022-03-21)

• Replace deprecated use of Storage by MappingStorage. [rnix]

• Replace deprecated use of Nodify by MappingNode. [rnix]

• Replace deprecated use of Adopt by MappingAdopt. [rnix]

• Replace deprecated use of NodeChildValidate by MappingConstraints. [rnix]

• Replace deprecated use of allow_non_node_childs by child_constraints. [rnix]

1.4 (2021-10-21)

• Implement _list_factory on Podict and OOBTodict and use PersistentList for internal double linked list triples to allow transaction property detect changes. [rnix, jensens]

• Drop ZODB3. [rnix]

1.3 (2020-07-09)

• Access attrs when initializing nodes with ZODBAttributes behavior applied to avoid lazy creation. Needed to prevent _p_changed being set on first access. [rnix, 2020-06-23]

• Access storage when initializing nodes with PodictStorage or OOBTodictStorage behaviors applied to avoid lazy creation. Needed to prevent _p_changed being set on first access. [rnix, 2020-06-23]

• Use plumb instead of overriding __setattr__ to change __parent__ name to _v_parent on ZODBBehavior. [rnix, 2020-06-23]

• Use plumb instead of overriding __getitem__ to set parent on ZODBBehavior. [rnix, 2020-02-28]

1.2 (2017-07-18)

• Add python 3 support. [rnix, 2017-06-24]

• Add keys to OOBTodict and accept any number of *args and **kw to match expected contract by OOBTree and Fix tests with ZODB 5. [rnix, 2017-06-22]

• Add __nonzero__ and __bool__ to OOBTodict in order to make it work properly with ZODB 5. [rnix, 2017-06-22]

• Use @property and @property.setter for OOBTodict.lh and OOBTodict.lt. [rnix, 2017-06-22]

1.1.1

• Change ZODB install requirement to ZODB3. Latter one is a meta package as of version 3.11.0 and installs ZODB [rnix, 2017-06-19]

1.1

• Remove superfluous __repr__ function from OOBTodict. odict package properly outputs class name as of version 1.6.2. [rnix, 2017-06-14]

• Fix volatile_property to work on classes overwriting __getattr__. [rnix, 2017-06-14]

• Use plumbing decorator instead of __metaclass__ and __plumbing__ class attributes. [rnix, 2017-06-14]

1.0.1

• Add maintenance utilities. [rnix, 2014-05-13]

• Cleanup tests. [rnix, 2014-05-13]

1.0

• initial [rnix]

License

Copyright (c) 2012-2021, BlueDynamics Alliance, Austria, Germany, Switzerland Copyright (c) 2021-2025, Node 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.