diff options
| author | Michael Merickel <michael@merickel.org> | 2015-02-17 19:02:14 -0600 |
|---|---|---|
| committer | Michael Merickel <michael@merickel.org> | 2015-02-17 19:02:14 -0600 |
| commit | bba15920ee77a626c2ea3636d9d3b4f8d571afa6 (patch) | |
| tree | 0e323159bcca6c78fcff408e465bd0b622ec0b3c | |
| parent | c0063b33e3b570120aab09b7d0a0adcf31c8705c (diff) | |
| download | pyramid-bba15920ee77a626c2ea3636d9d3b4f8d571afa6.tar.gz pyramid-bba15920ee77a626c2ea3636d9d3b4f8d571afa6.tar.bz2 pyramid-bba15920ee77a626c2ea3636d9d3b4f8d571afa6.zip | |
avoid saying order=0, instead say PHASE3_CONFIG
| -rw-r--r-- | docs/narr/extconfig.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/narr/extconfig.rst b/docs/narr/extconfig.rst index 47f2fcb46..d17842bf2 100644 --- a/docs/narr/extconfig.rst +++ b/docs/narr/extconfig.rst @@ -238,8 +238,9 @@ actions. The logic within actions is deferred until a call to commit-time. During a commit cycle conflicts are resolved, actions are ordered and executed. -By default, almost every action in Pyramid has an ``order`` of ``0``. Every -action within the same order-level will be executed in the order it was called. +By default, almost every action in Pyramid has an ``order`` of +:const:`pyramid.config.PHASE3_CONFIG`. Every action within the same order-level +will be executed in the order it was called. This means that if an action must be reliably executed before or after another action, the ``order`` must be defined explicitly to make this work. For example, views are dependent on routes being defined. Thus the action created |