node The node
Download

node Ranking & Summary

node Tags

Python library library Zope zodict successor zodict

node Description

The node node is the successor of zodict.Data structures could be described as tree. Some are by nature treeish, like XML documents, LDAP directories or filesystem directory trees, while others could be treaten as. Consider SQL as example. A Database has tables, these contain rows which contain columns.Next, python has elegant ways for customizing all sorts of datamodel related API. The dictionary container type fits almost completely the purpose of representing a node of a tree. The same API is also described in zope.interface.common.mapping.IFullMapping. Additionaly a node must provide hierarchy information. In this case the contract of zope.location.interfaces.ILocation is used.Having data structures as such trees has some advantages: * Unified data access API to different data models and/or sources * Trees are traversable in both directions * Once in memory, node trees are fast to deal with * Software working on node trees may not need to know about internal data structures, as long as the node tree implementation provides the correct interface contractsUsage:node ships with some "ready-to-import-and-use" nodes.An unordered node. This can be used as base for trees where oder of items doesn't matter.:>>> from node.base import BaseNode>>> root = BaseNode(name='root')>>> root = BaseNode()>>> root.printtree()< class 'node.base.BaseNode' >: root < class 'node.base.BaseNode' >: childAn ordered node. Order of items is preserved.:>>> from node.base import OrderedNode>>> root = OrderedNode(name='orderedroot')>>> root = OrderedNode()>>> root = OrderedNode()>>> root.printtree()< class 'node.base.OrderedNode' >: orderedroot < class 'node.base.OrderedNode' >: foo < class 'node.base.OrderedNode' >: bar>>> root.items()A full API description of the node interface can be found at node.interfaces.INode.A more fine granular control of node functionalitynode utilizes the plumber package.Thus, different behaviors of nodes are provided by plumbing parts. Read the documentation of plumber for details about the plumbing system. >>> from plumber import plumber >>> from node.parts import ( ... Nodespaces, ... Attributes, ... Lifecycle, ... NodeChildValidate, ... Adopt, ... DefaultInit, ... Nodify, ... OdictStorage, ... ) >>> class CustomNode(object): ... __metaclass__ = plumber ... __plumbing__ = ( ... Nodespaces, ... Attributes, ... Lifecycle, ... NodeChildValidate, ... Adopt, ... DefaultInit, ... Nodify, ... OdictStorage, ... ) >>> dir(CustomNode) As dir call shows, CustomNode class was plumbed using given parts, now defining a complete INode implementation with some additional behaviours and is now ready to use:>>> node = CustomNode()>>> node = CustomNode()>>> node.printtree()< class 'CustomNode' >: None < class 'CustomNode' >: child>>> from node.interfaces import INode>>> INode.providedBy(node)TruePartsnode package provides several plumbing parts:Alias Provide node.interfaces.IAlias on node class.Attributes Provide node.interfaces.IAttributes on node class, requires Nodespaces part.Adopt Set __name__ and __parent__ attributes automatically during node tree manipulation.AsAttrAccess Provide node.interfaces.IAsAttrAccess on node class.Lifecycle Provide node.interfaces.ILifecycle on node class.Nodespaces Provide node.interfaces.INodespaces on node class.DefaultInit Provide a default __init__ function on node class.Nodify Hook basic INode API on node class.Order Provide node.interfaces.IOrder on node class.Reference Provide node.interfaces.IReference on node class.DictStorage Provide data related methods utilizing dict.OdictStorage Provide data related methods utilizing odict.TestCoverageSummary of the test coverage report:lines cov% module 106 88% node.aliasing 27 100% node.base 24 58% node.events 127 86% node.interfaces 23 95% node.locking 11 100% node.parts.__init__ 46 100% node.parts.alias 38 100% node.parts.attributes 53 92% node.parts.cache 71 74% node.parts.common 54 90% node.parts.lifecycle 113 100% node.parts.mapping 31 100% node.parts.nodespace 67 97% node.parts.nodify 65 100% node.parts.order 81 100% node.parts.reference 34 100% node.parts.storage 73 98% node.utils Requirements: · Python What's New in This Release: · Provide node.base.Node with same behavior like zodict.Node for migration purposes.

node Related Software