Context lifecycle execution in Flask - Step-by-Step Execution

Concept Flow - Context lifecycle execution

Start Request

↓

Create Request Context

↓

Push Context

↓

Handle Request

↓

Pop Context

↓

End Request

This flow shows how Flask creates and manages the request context during a web request lifecycle.

Execution Sample

Flask

from flask import Flask, request
app = Flask(__name__)

@app.route('/')
def index():
    return f"Path: {request.path}"

A simple Flask app that uses the request context to access the current request path.

Execution Table

Step	Action	Context State	Result
1	Start Request	No context	Waiting for request data
2	Create Request Context	Request context created	Context holds request info
3	Push Context	Context active	Context is now accessible globally
4	Handle Request	Context active	Function 'index' runs, accesses request.path
5	Return Response	Context active	Response with path string generated
6	Pop Context	Context removed	Context cleaned up, no longer accessible
7	End Request	No context	Request lifecycle complete

💡 Request ends, context is popped and cleaned up to avoid leaks

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 6	Final
request context	None	Created	Active	Removed	None
request.path	N/A	N/A	Available	Unavailable	N/A

Key Moments - 2 Insights

Why can't we access 'request.path' before the context is pushed?

Because the request context is not active before step 3, 'request' is not bound to any data yet (see execution_table step 3).

What happens if the context is not popped after the request?

The context would remain active and could cause memory leaks or incorrect data sharing between requests (see execution_table step 6).

Visual Quiz - 3 Questions

Look at the execution table, at which step is the request context first accessible?

A Step 2

B Step 4

C Step 3

D Step 6

💡 Hint

Check the 'Context State' column for when context becomes 'active'

At which step does the Flask app run the route function to handle the request?

A Step 4

B Step 3

C Step 5

D Step 6

💡 Hint

Look for 'Handle Request' in the 'Action' column

If the context is not popped, what is the likely effect?

A Request handling stops immediately

B Memory leaks and stale data may occur

C Response is never sent

D Request context is recreated automatically

💡 Hint

Refer to the 'key_moments' section about context cleanup

Concept Snapshot

Flask Context Lifecycle:
1. Start request, no context.
2. Create request context with request data.
3. Push context to make it active.
4. Handle request using context (e.g., request.path).
5. Return response.
6. Pop context to clean up after request.

Full Transcript

In Flask, each web request starts with no active context. Flask creates a request context holding data like the URL path. This context is pushed to become active, allowing code to access request details globally. The route function runs using this context. After the response is sent, Flask pops the context to clean up. This lifecycle prevents data leaks and ensures each request is isolated.

Practice

1. What is the main purpose of Flask's before_request function in the context lifecycle?

easy

A. To run code before each request to prepare data or resources

B. To clean up resources after a request finishes

C. To handle errors during a request

D. To define the URL routes for the application

Solution

1. Step 1: Understand the role of before_request

   This function runs before each request to set up anything needed during the request.

2. Step 2: Compare with other lifecycle hooks

   after_request cleans up after requests, error handlers manage errors, and routes define URLs.

3. Final Answer:

   To run code before each request to prepare data or resources -> Option A

4. Quick Check:

   before_request runs before request [OK]

Hint: Remember: before_request runs setup code before handling requests [OK]

Common Mistakes:

• Confusing before_request with after_request
• Thinking before_request handles errors
• Mixing route definitions with lifecycle hooks

2. Which of the following is the correct way to store data for the current request using Flask's context?

easy

A. Store data in the g object inside a before_request function

B. Use a global variable outside the request

C. Save data in a class variable of the Flask app

D. Write data directly to the response object

Solution

1. Step 1: Identify how Flask manages request-specific data

   Flask provides the g object to store data unique to each request.

2. Step 2: Confirm correct usage

   Using g inside before_request ensures data is set up before route handlers run.

3. Final Answer:

   Store data in the g object inside a before_request function -> Option A

4. Quick Check:

   g stores request data [OK]

Hint: Use g for request data, not globals [OK]

Common Mistakes:

• Using global variables that persist across requests
• Trying to store request data in app class variables
• Modifying the response object directly for data storage

3. Given this Flask code snippet, what will be printed when a request is made to /hello?

from flask import Flask, g
app = Flask(__name__)

@app.before_request
def before():
    g.message = 'Hi'

@app.route('/hello')
def hello():
    return g.message + ' there!'

medium

A. there!

B. Error: g.message not set

C. Hi there!

D. Hi

Solution

1. Step 1: Analyze the before_request function

   The function sets g.message to 'Hi' before the route runs.

2. Step 2: Check the route handler output

   The route returns g.message + ' there!', which becomes 'Hi there!'.

3. Final Answer:

   Hi there! -> Option C

4. Quick Check:

   g.message set before route [OK]

Hint: before_request sets g data used in routes [OK]

Common Mistakes:

• Assuming g.message is not set yet
• Forgetting before_request runs before routes
• Expecting an error due to missing g attribute

4. What is wrong with this Flask code that tries to use g outside a request context?

from flask import Flask, g
app = Flask(__name__)

g.message = 'Hello'

@app.route('/')
def index():
    return g.message

medium

A. The g object cannot store strings

B. The route function is missing a return statement

C. The app is missing a secret key

D. Accessing g outside a request causes a runtime error

Solution

1. Step 1: Identify where g is assigned

   g.message = 'Hello' is set outside any request or app context.

2. Step 2: Understand Flask context rules

   g is only available during a request context; accessing it outside causes an error.

3. Final Answer:

   Accessing g outside a request causes a runtime error -> Option D

4. Quick Check:

   g only valid inside requests [OK]

Hint: Set g only inside request functions [OK]

Common Mistakes:

• Setting g variables globally outside requests
• Confusing g with global variables
• Ignoring Flask's context lifecycle rules

5. You want to log the time taken by each request in your Flask app. Which is the best way to do this using context lifecycle hooks?

hard

A. Use teardown_request to set start time and before_request to log duration

B. Use before_request to store start time in g, and after_request to calculate and log duration

C. Log the time only inside the route without lifecycle hooks

D. Store start time in a global variable and log it in the route function

Solution

1. Step 1: Use before_request to mark start time

   Store the current time in g.start_time before the request runs.

2. Step 2: Use after_request to calculate duration and log

   Calculate elapsed time using current time minus g.start_time and log it, then return the response.

3. Final Answer:

   Use before_request to store start time in g, and after_request to calculate and log duration -> Option B

4. Quick Check:

   Use before_request and after_request for timing [OK]

Hint: Start timer before, log after request finishes [OK]

Common Mistakes:

• Using global variables instead of g
• Logging time only inside routes missing full request duration
• Mixing up lifecycle hook order