indentation
This commit is contained in:
10
CHANGES.txt
10
CHANGES.txt
@@ -152,8 +152,8 @@ Features
|
||||
|
||||
If the things you're trying to defer aren't callables like ``validator``,
|
||||
but they're instead just plain attributes like ``missing`` or ``default``,
|
||||
instead of using a ``colander.deferred``, you can use ``after_bind`` to
|
||||
set attributes of the schemanode that rely on binding variables::
|
||||
instead of using a ``colander.deferred``, you can use ``after_bind`` to set
|
||||
attributes of the schemanode that rely on binding variables::
|
||||
|
||||
from colander import SchemaNode
|
||||
|
||||
@@ -220,9 +220,9 @@ Features
|
||||
|
||||
Ordering of child schema nodes when inheritance is used works like this:
|
||||
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
|
||||
on. So the deepest class' nodes come first in the relative ordering of
|
||||
schema nodes, then the next deepest, and so on. For example::
|
||||
consulted first for nodes, then the next deepest, then the next, and so on.
|
||||
So the deepest class' nodes come first in the relative ordering of schema
|
||||
nodes, then the next deepest, and so on. For example::
|
||||
|
||||
class One(colander.Schema):
|
||||
a = colander.SchemaNode(
|
||||
|
||||
Reference in New Issue
Block a user