From c1b032a5a31a23d28767d2fce66d6a0f5b835791 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Fri, 24 Dec 2010 17:31:58 -0500 Subject: internal ordering --- docs/narr/advconfig.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs') 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. -- cgit v1.2.3