|
|
|
@ -162,11 +162,11 @@ function, you can pass ``current_app._get_current_object()`` as sender.
|
|
|
|
|
Signals and Flask's Request Context |
|
|
|
|
----------------------------------- |
|
|
|
|
|
|
|
|
|
Signals fully support :ref:`reqcontext` when receiving signals. Context-local |
|
|
|
|
variables are consistently available between :data:`~flask.request_started` and |
|
|
|
|
:data:`~flask.request_finished`, so you can rely on :class:`flask.g` and others |
|
|
|
|
as needed. Note the limitations described in :ref:`signals-sending` and the |
|
|
|
|
:data:`~flask.request_tearing_down` signal. |
|
|
|
|
Signals fully support :ref:`request-context` when receiving signals. |
|
|
|
|
Context-local variables are consistently available between |
|
|
|
|
:data:`~flask.request_started` and :data:`~flask.request_finished`, so you can |
|
|
|
|
rely on :class:`flask.g` and others as needed. Note the limitations described |
|
|
|
|
in :ref:`signals-sending` and the :data:`~flask.request_tearing_down` signal. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Decorator Based Signal Subscriptions |
|
|
|
|