diff options
| author | Chris McDonough <chrism@agendaless.com> | 2009-12-11 20:11:53 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2009-12-11 20:11:53 +0000 |
| commit | 5f5f5c511e5338be9a68f58b01c0f81c70337d25 (patch) | |
| tree | fd83af5ee4962ed652eee9cb5c8dfc6e98e81e86 /docs/narr/threadlocals.rst | |
| parent | 6b3f9605f81a0c08cadfca163e322033d390900a (diff) | |
| download | pyramid-5f5f5c511e5338be9a68f58b01c0f81c70337d25.tar.gz pyramid-5f5f5c511e5338be9a68f58b01c0f81c70337d25.tar.bz2 pyramid-5f5f5c511e5338be9a68f58b01c0f81c70337d25.zip | |
Fix typos pointed out by Steve Schmechel.
Diffstat (limited to 'docs/narr/threadlocals.rst')
| -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 d6c3c9b0a..476b179ec 100644 --- a/docs/narr/threadlocals.rst +++ b/docs/narr/threadlocals.rst @@ -89,7 +89,7 @@ Why You Shouldn't Abuse Thread Locals You probably should almost never use the ``get_current_request`` or ``get_current_registry`` functions, except perhaps in tests. In -particular, it's almost always usually a mistake to use +particular, it's almost always a mistake to use ``get_current_request`` or ``get_current_registry`` in application code because its usage makes it possible to write code that can be neither easily tested nor scripted. Inappropriate usage is defined as @@ -118,7 +118,7 @@ follows: lead to sadness later. - Neither ``get_current_request`` nor ``get_current_registry`` should - never be called within application-specific forks of third-party + ever be called within application-specific forks of third-party library code. The library you've forked almost certainly has nothing to do with :mod:`repoze.bfg`, and making it dependent on repoze.bfg (rather than making your :mod:`repoze.bfg` application |