forked from orbit-oss/flask
fix codespell findings
This commit is contained in:
parent
5880befcd2
commit
9b74a90dd3
4 changed files with 4 additions and 5 deletions
|
|
@ -12,8 +12,7 @@ repos:
|
||||||
rev: 63c8f8312b7559622c0d82815639671ae42132ac # frozen v2.4.1
|
rev: 63c8f8312b7559622c0d82815639671ae42132ac # frozen v2.4.1
|
||||||
hooks:
|
hooks:
|
||||||
- id: codespell
|
- id: codespell
|
||||||
additional_dependencies:
|
args: ['--write-changes']
|
||||||
- tomli
|
|
||||||
- repo: https://github.com/pre-commit/pre-commit-hooks
|
- repo: https://github.com/pre-commit/pre-commit-hooks
|
||||||
rev: 3e8a8703264a2f4a69428a0aa4dcb512790b2c8c # frozen: v6.0.0
|
rev: 3e8a8703264a2f4a69428a0aa4dcb512790b2c8c # frozen: v6.0.0
|
||||||
hooks:
|
hooks:
|
||||||
|
|
|
||||||
|
|
@ -119,7 +119,7 @@ The context will have the same lifetime as an activity, such as a request, CLI
|
||||||
command, or ``with`` block. Various callbacks and signals registered with the
|
command, or ``with`` block. Various callbacks and signals registered with the
|
||||||
app will be run during the context.
|
app will be run during the context.
|
||||||
|
|
||||||
When a Flask application handles a request, it pushes a requet context
|
When a Flask application handles a request, it pushes a request context
|
||||||
to set the active application and request data. When it handles a CLI command,
|
to set the active application and request data. When it handles a CLI command,
|
||||||
it pushes an app context to set the active application. When the activity ends,
|
it pushes an app context to set the active application. When the activity ends,
|
||||||
it pops that context. Proxy objects like :data:`.request`, :data:`.session`,
|
it pops that context. Proxy objects like :data:`.request`, :data:`.session`,
|
||||||
|
|
|
||||||
|
|
@ -462,7 +462,7 @@ broad overview. First it needs to be imported.
|
||||||
If you have some experience with Python you might be wondering how that object
|
If you have some experience with Python you might be wondering how that object
|
||||||
can be global when Flask handles multiple requests at a time. The answer is
|
can be global when Flask handles multiple requests at a time. The answer is
|
||||||
that :data:`.request` is actually a proxy, pointing at whatever request is
|
that :data:`.request` is actually a proxy, pointing at whatever request is
|
||||||
currently being handled by a given worker, which is managed interanlly by Flask
|
currently being handled by a given worker, which is managed internally by Flask
|
||||||
and Python. See :doc:`/appcontext` for much more information.
|
and Python. See :doc:`/appcontext` for much more information.
|
||||||
|
|
||||||
The current request method is available in the :attr:`~.Request.method`
|
The current request method is available in the :attr:`~.Request.method`
|
||||||
|
|
|
||||||
|
|
@ -183,7 +183,7 @@ For template tests, use the :meth:`~.Flask.template_test` decorator or
|
||||||
method.
|
method.
|
||||||
|
|
||||||
The same methods also exist on :class:`.Blueprint`, prefixed with ``app_`` to
|
The same methods also exist on :class:`.Blueprint`, prefixed with ``app_`` to
|
||||||
indicate that the registered functions will be avaialble to all templates, not
|
indicate that the registered functions will be available to all templates, not
|
||||||
only when rendering from within the blueprint.
|
only when rendering from within the blueprint.
|
||||||
|
|
||||||
The Jinja environment is also available as :attr:`~.Flask.jinja_env`. It may be
|
The Jinja environment is also available as :attr:`~.Flask.jinja_env`. It may be
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue