From 2386bb2b774ee745f7923a3edec734332b38658a Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Thu, 8 Sep 2011 03:48:26 -0400 Subject: require, not construct --- docs/narr/introduction.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst index df1f3f954..3c3c88591 100644 --- a/docs/narr/introduction.rst +++ b/docs/narr/introduction.rst @@ -458,12 +458,13 @@ Example: :ref:`sessions_chapter`. No singletons ~~~~~~~~~~~~~ -Pyramid is written in such a way that it has exactly zero "singleton" data -structures. Or, put another way, Pyramid constructs no "mutable globals". -Or put even a different way, an import of a Pyramid application needn't have -any "import time side effects". This is esoteric-sounding, but if you've -ever tried to cope with parameterizing a Django "settings.py" file for -multiple installations of the same application, or if you've ever needed to +Pyramid is written in such a way that it requires your application to have +exactly zero "singleton" data structures. Or, put another way, Pyramid +doesn't requires you to construct any "mutable globals". Or put even a +different way, an import of a Pyramid application needn't have any "import +time side effects". This is esoteric-sounding, but if you've ever tried to +cope with parameterizing a Django "settings.py" file for multiple +installations of the same application, or if you've ever needed to monkey-patch some framework fixture so that it behaves properly for your use case, or if you've ever wanted to deploy your system using an asynchronous server, you'll end up appreciating this feature. It just won't be a problem. -- cgit v1.2.3