summaryrefslogtreecommitdiff
path: root/docs/narr/advconfig.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2010-12-24 17:31:58 -0500
committerChris McDonough <chrism@plope.com>2010-12-24 17:31:58 -0500
commitc1b032a5a31a23d28767d2fce66d6a0f5b835791 (patch)
tree131d6ba0ade04b6d547eeae83dddd744786bf610 /docs/narr/advconfig.rst
parentef492de9cc24c573faaf12d654267480202fe645 (diff)
downloadpyramid-c1b032a5a31a23d28767d2fce66d6a0f5b835791.tar.gz
pyramid-c1b032a5a31a23d28767d2fce66d6a0f5b835791.tar.bz2
pyramid-c1b032a5a31a23d28767d2fce66d6a0f5b835791.zip
internal ordering
Diffstat (limited to 'docs/narr/advconfig.rst')
-rw-r--r--docs/narr/advconfig.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/narr/advconfig.rst b/docs/narr/advconfig.rst
index 2ed0a96ab..68e3796fe 100644
--- a/docs/narr/advconfig.rst
+++ b/docs/narr/advconfig.rst
@@ -378,4 +378,10 @@ The same is untrue when you use an *autocommitting* configurator (see
used, two-phase configuration is disabled, and configuration statements must
be ordered in dependency order.
+Some configuration methods, such as
+:meth:`pyramid.config.Configurator.add_route` and
+:meth:`pyramid.config.Configurator.add_handler` have internal ordering
+constraints: they routes they imply require relative ordering. Such ordering
+constraints are not absolved by two-phase configuration. Routes are still
+added in configuration execution order.