Skip to content

Minor documentation #5877

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
harshitasurana wants to merge 2 commits into from
+0 −12
Closed

Minor documentation #5877

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
da431f7
Update README
harshitasurana Jan 3, 2026
6c6180b
[pre-commit.ci lite] apply automatic fixes
pre-commit-ci-lite[bot] Jan 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 0 additions & 12 deletions docs/lifecycle.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,15 +157,3 @@ parts that you can use to customize its behavior.
#. The app context is popped, :data:`.current_app`, :data:`.g`, :data:`.request`,
and :data:`.session` are no longer available.
#. The :data:`.appcontext_popped` signal is sent.

When executing a CLI command or plain app context without request data, the same
order of steps is followed, omitting the steps that refer to the request.

A :class:`Blueprint` can add handlers for these events that are specific to the
blueprint. The handlers for a blueprint will run if the blueprint
owns the route that matches the request.

There are even more decorators and customization points than this, but that aren't part
of every request lifecycle. They're more specific to certain things you might use during
a request, such as templates, building URLs, or handling JSON data. See the rest of this
documentation, as well as the :doc:`api` to explore further.