mirror of https://github.com/pallets/flask.git
fix grammar in links to app and request context
This commit is contained in:
parent
b4094b35ef
commit
1a40d9b976
|
@ -8,7 +8,7 @@ a request, CLI command, or other activity. Rather than passing the
|
||||||
application around to each function, the :data:`current_app` and
|
application around to each function, the :data:`current_app` and
|
||||||
:data:`g` proxies are accessed instead.
|
:data:`g` proxies are accessed instead.
|
||||||
|
|
||||||
This is similar to the :doc:`/reqcontext`, which keeps track of
|
This is similar to :doc:`/reqcontext`, which keeps track of
|
||||||
request-level data during a request. A corresponding application context
|
request-level data during a request. A corresponding application context
|
||||||
is pushed when a request context is pushed.
|
is pushed when a request context is pushed.
|
||||||
|
|
||||||
|
|
|
@ -8,7 +8,7 @@ request. Rather than passing the request object to each function that
|
||||||
runs during a request, the :data:`request` and :data:`session` proxies
|
runs during a request, the :data:`request` and :data:`session` proxies
|
||||||
are accessed instead.
|
are accessed instead.
|
||||||
|
|
||||||
This is similar to the :doc:`/appcontext`, which keeps track of the
|
This is similar to :doc:`/appcontext`, which keeps track of the
|
||||||
application-level data independent of a request. A corresponding
|
application-level data independent of a request. A corresponding
|
||||||
application context is pushed when a request context is pushed.
|
application context is pushed when a request context is pushed.
|
||||||
|
|
||||||
|
@ -33,8 +33,8 @@ Lifetime of the Context
|
||||||
-----------------------
|
-----------------------
|
||||||
|
|
||||||
When a Flask application begins handling a request, it pushes a request
|
When a Flask application begins handling a request, it pushes a request
|
||||||
context, which also pushes an :doc:`/appcontext`. When the request ends
|
context, which also pushes an :doc:`app context </appcontext>`. When the
|
||||||
it pops the request context then the application context.
|
request ends it pops the request context then the application context.
|
||||||
|
|
||||||
The context is unique to each thread (or other worker type).
|
The context is unique to each thread (or other worker type).
|
||||||
:data:`request` cannot be passed to another thread, the other thread
|
:data:`request` cannot be passed to another thread, the other thread
|
||||||
|
|
|
@ -21,8 +21,7 @@ that these functions are not only there for interactive shell usage, but
|
||||||
also for unit testing and other situations that require a faked request
|
also for unit testing and other situations that require a faked request
|
||||||
context.
|
context.
|
||||||
|
|
||||||
Generally it's recommended that you read the :doc:`reqcontext`
|
Generally it's recommended that you read :doc:`reqcontext` first.
|
||||||
chapter of the documentation first.
|
|
||||||
|
|
||||||
Command Line Interface
|
Command Line Interface
|
||||||
----------------------
|
----------------------
|
||||||
|
|
Loading…
Reference in New Issue