diff options
| author | Carlos de la Guardia <cguardia@yahoo.com> | 2010-03-29 21:42:56 +0000 |
|---|---|---|
| committer | Carlos de la Guardia <cguardia@yahoo.com> | 2010-03-29 21:42:56 +0000 |
| commit | 219ba8e0b31e5e7eb10c2f6e14964d804e100c2d (patch) | |
| tree | 809a6ceeee7b08d07ce5c94c93e2769fc4d50325 | |
| parent | dbf83154af5267f7cf0da13e271df1d8834ad309 (diff) | |
| download | pyramid-219ba8e0b31e5e7eb10c2f6e14964d804e100c2d.tar.gz pyramid-219ba8e0b31e5e7eb10c2f6e14964d804e100c2d.tar.bz2 pyramid-219ba8e0b31e5e7eb10c2f6e14964d804e100c2d.zip | |
quick fixes
| -rw-r--r-- | docs/narr/threadlocals.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/threadlocals.rst b/docs/narr/threadlocals.rst index a2f5cc192..df7023a1a 100644 --- a/docs/narr/threadlocals.rst +++ b/docs/narr/threadlocals.rst @@ -33,7 +33,7 @@ For historical reasons, however, thread local variables are indeed consulted by various :mod:`repoze.bfg` API functions. For example, the implementation of the :mod:`repoze.bfg.security` function named :func:`repoze.bfg.security.authenticated_userid` retrieves the thread -local :term:`application registry` as a matter of course to find a +local :term:`application registry` as a matter of course to find an :term:`authentication policy`. It uses the :func:`repoze.bfg.threadlocal.get_current_registry` function to retrieve the application registry, from which it looks up the @@ -84,7 +84,7 @@ and pop the threadlocal stack when the system is under test. See Scripts which use :mod:`repoze.bfg` machinery but never actually start a WSGI server or receive requests via HTTP such as scripts which use -the :mod:`repoze.bfg.scripting`` API will never cause any Router code +the :mod:`repoze.bfg.scripting` API will never cause any Router code to be executed. However, the :mod:`repoze.bfg.scripting` APIs also push some values on to the thread locals stack as a matter of course. Such scripts should expect the |