/usr/share/doc/python-werkzeug-doc/html/_sources/local.txt is in python-werkzeug-doc 0.10.4+dfsg1-1ubuntu1.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 | ==============
Context Locals
==============
.. module:: werkzeug.local
Sooner or later you have some things you want to have in every single view
or helper function or whatever. In PHP the way to go are global
variables. However, that isn't possible in WSGI applications without a
major drawback: As soon as you operate on the global namespace your
application isn't thread-safe any longer.
The Python standard library comes with a utility called "thread locals".
A thread local is a global object in which you can put stuff in and get back
later in a thread-safe way. That means whenever you set or get an object
on a thread local object, the thread local object checks in which
thread you are and retrieves the correct value.
This, however, has a few disadvantages. For example, besides threads there
are other ways to handle concurrency in Python. A very popular approach
is greenlets. Also, whether every request gets its own thread is not
guaranteed in WSGI. It could be that a request is reusing a thread from
before, and hence data is left in the thread local object.
Here's a simple example of how one could use werkzeug.local::
from werkzeug.local import Local, LocalManager
local = Local()
local_manager = LocalManager([local])
def application(environ, start_response):
local.request = request = Request(environ)
...
application = local_manager.make_middleware(application)
This binds the request to `local.request`. Every other piece of code executed
after this assignment in the same context can safely access local.request and
will get the same request object. The `make_middleware` method on the local
manager ensures that all references to the local objects are cleared up after
the request.
The same context means the same greenlet (if you're using greenlets) in
the same thread and same process.
If a request object is not yet set on the local object and you try to
access it, you will get an `AttributeError`. You can use `getattr` to avoid
that::
def get_request():
return getattr(local, 'request', None)
This will try to get the request or return `None` if the request is not
(yet?) available.
Note that local objects cannot manage themselves, for that you need a local
manager. You can pass a local manager multiple locals or add additionals
later by appending them to `manager.locals` and everytime the manager
cleans up it will clean up all the data left in the locals for this
context.
.. autofunction:: release_local
.. autoclass:: LocalManager
:members: cleanup, make_middleware, middleware, get_ident
.. autoclass:: LocalStack
:members: push, pop, top
.. autoclass:: LocalProxy
:members: _get_current_object
Keep in mind that ``repr()`` is also forwarded, so if you want to find
out if you are dealing with a proxy you can do an ``isinstance()`` check:
.. sourcecode:: pycon
>>> from werkzeug.local import LocalProxy
>>> isinstance(request, LocalProxy)
True
You can also create proxy objects by hand:
.. sourcecode:: python
from werkzeug.local import Local, LocalProxy
local = Local()
request = LocalProxy(local, 'request')
|