openstack/deb-python-colander
Code Issues Proposed changes

indentation

Browse Source
This commit is contained in:
Chris McDonough
2012-10-09 03:02:36 -04:00
parent 718ba03cbb
commit 10a30c85ee
1 changed files with 54 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
CHANGES.txt
View File

@@ -152,8 +152,8 @@ Features
If the things you're trying to defer aren't callables like ``validator``, If the things you're trying to defer aren't callables like ``validator``,
but they're instead just plain attributes like ``missing`` or ``default``, but they're instead just plain attributes like ``missing`` or ``default``,
instead of using a ``colander.deferred``, you can use ``after_bind`` to instead of using a ``colander.deferred``, you can use ``after_bind`` to set
set attributes of the schemanode that rely on binding variables:: attributes of the schemanode that rely on binding variables::
from colander import SchemaNode from colander import SchemaNode
@@ -220,9 +220,9 @@ Features
Ordering of child schema nodes when inheritance is used works like this: Ordering of child schema nodes when inheritance is used works like this:
the "deepest" SchemaNode class in the MRO of the inheritance chain is the "deepest" SchemaNode class in the MRO of the inheritance chain is
consulted first for nodes, then the next deepest, then the next, and so consulted first for nodes, then the next deepest, then the next, and so on.
on. So the deepest class' nodes come first in the relative ordering of So the deepest class' nodes come first in the relative ordering of schema
schema nodes, then the next deepest, and so on. For example:: nodes, then the next deepest, and so on. For example::
class One(colander.Schema): class One(colander.Schema):
a = colander.SchemaNode( a = colander.SchemaNode(