summaryrefslogtreecommitdiff
path: root/docs/narr/configuration.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2010-11-04 12:20:32 -0400
committerChris McDonough <chrism@plope.com>2010-11-04 12:20:32 -0400
commit7a3fd94d1066363c0f8e97215503d7118e06ead2 (patch)
treea4a65360d53103401ff400f3fa189496c7b6d7da /docs/narr/configuration.rst
parente19eaeb283dbfe6b64d963cafcc46837eaf1e76b (diff)
downloadpyramid-7a3fd94d1066363c0f8e97215503d7118e06ead2.tar.gz
pyramid-7a3fd94d1066363c0f8e97215503d7118e06ead2.tar.bz2
pyramid-7a3fd94d1066363c0f8e97215503d7118e06ead2.zip
simplify
Diffstat (limited to 'docs/narr/configuration.rst')
-rw-r--r--docs/narr/configuration.rst7
1 files changed, 0 insertions, 7 deletions
diff --git a/docs/narr/configuration.rst b/docs/narr/configuration.rst
index 82d0c8dda..dc89b42cb 100644
--- a/docs/narr/configuration.rst
+++ b/docs/narr/configuration.rst
@@ -24,13 +24,6 @@ itself. When you plug code into the :mod:`pyramid` framework, you are
"configuring" :mod:`pyramid` for the purpose of creating a particular
application deployment.
-There are two different mechanisms you may use to configure :mod:`pyramid` to
-create an application: *imperative* configuration and *declarative*
-configuration. We'll be using primarily the *imperative* configuration
-method in this book, for the sake of brevity and simplicity. For information
-about how to define application configuration declaratively, see
-:ref:`declarative_chapter`.
-
.. index::
single: imperative configuration