diff options
| author | Chris McDonough <chrism@plope.com> | 2010-12-09 02:50:15 -0500 |
|---|---|---|
| committer | Chris McDonough <chrism@plope.com> | 2010-12-09 02:50:15 -0500 |
| commit | f360d9e6d9689dfe92a950e97e7e19c414655997 (patch) | |
| tree | f0456af418ecfaf7d5a342556d2c5786b2aee979 /docs/narr/hooks.rst | |
| parent | c18b16d293ee60117747f0de042e2d75361d1fd8 (diff) | |
| parent | 13173e9e1d1c5f3873e8bfed91e6f3ed561dafaf (diff) | |
| download | pyramid-f360d9e6d9689dfe92a950e97e7e19c414655997.tar.gz pyramid-f360d9e6d9689dfe92a950e97e7e19c414655997.tar.bz2 pyramid-f360d9e6d9689dfe92a950e97e7e19c414655997.zip | |
Merge branch 'twophase'
Conflicts:
pyramid/configuration.py
Diffstat (limited to 'docs/narr/hooks.rst')
| -rw-r--r-- | docs/narr/hooks.rst | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/narr/hooks.rst b/docs/narr/hooks.rst index ada96f897..10f463a17 100644 --- a/docs/narr/hooks.rst +++ b/docs/narr/hooks.rst @@ -29,7 +29,7 @@ class as the ``context`` of the view configuration. If your application uses :term:`imperative configuration`, you can replace the Not Found view by using the - :meth:`pyramid.configuration.Configurator.add_view` method to + :meth:`pyramid.config.Configurator.add_view` method to register an "exception view": .. code-block:: python @@ -118,7 +118,7 @@ class as the ``context`` of the view configuration. If your application uses :term:`imperative configuration`, you can replace the Forbidden view by using the - :meth:`pyramid.configuration.Configurator.add_view` method to + :meth:`pyramid.config.Configurator.add_view` method to register an "exception view": .. code-block:: python @@ -368,13 +368,13 @@ In the below, we assume it lives in a package named Lastly, if you're doing imperative configuration, and you'd rather do it after you've already constructed a :term:`configurator` it can also be registered via the -:meth:`pyramid.configuration.Configurator.set_request_factory` +:meth:`pyramid.config.Configurator.set_request_factory` method: .. code-block:: python :linenos: - from pyramid.configuration import Configurator + from pyramid.config import Configurator from pyramid.request import Request class MyRequest(Request): @@ -435,13 +435,13 @@ named ``mypackage.mymodule``. Lastly, if you're doing imperative configuration, and you'd rather do it after you've already constructed a :term:`configurator` it can also be registered via the -:meth:`pyramid.configuration.Configurator.set_renderer_globals_factory` +:meth:`pyramid.config.Configurator.set_renderer_globals_factory` method: .. code-block:: python :linenos: - from pyramid.configuration import Configurator + from pyramid.config import Configurator def renderer_globals_factory(system): return {'a':1} @@ -474,7 +474,7 @@ that can be used for this purpose. For example: An object of this type is sent as an event just before a :term:`renderer` is invoked (but *after* the application-level renderer globals factory added via -:class:`pyramid.configuration.Configurator.set_renderer_globals_factory`, if +:class:`pyramid.config.Configurator.set_renderer_globals_factory`, if any, has injected its own keys into the renderer globals dictionary). If a subscriber attempts to add a key that already exist in the renderer @@ -659,7 +659,7 @@ performed, enabling you to set up the utility in advance: :linenos: from paste.httpserver import serve - from pyramid.configuration import Configurator + from pyramid.config import Configurator class UtilityImplementation: |