Context lifecycle execution in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the application context in Flask?

The application context in Flask holds data related to the app itself, like configuration and resources, making them accessible during a request or CLI command.

beginner

What does the request context in Flask contain?

The request context contains information about the current HTTP request, such as form data, headers, and session, allowing code to access request-specific data.

intermediate

When is the Flask application context pushed and popped?

The application context is pushed before handling a request or CLI command and popped after the request or command finishes, ensuring resources are available only when needed.

intermediate

Explain the order of context lifecycle during a Flask request.

First, Flask pushes the application context, then the request context. After processing, it pops the request context followed by the application context, cleaning up resources in reverse order.

advanced

How can you manually manage Flask contexts in your code?

You can manually push and pop contexts using 'app.app_context()' and 'app.test_request_context()' with 'with' statements to control when contexts are active.

Which context in Flask holds the current HTTP request data?

A Application context

B Database context

C Request context

D Session context

The request context contains data specific to the current HTTP request, such as form inputs and headers.

When does Flask pop the application context?

A During app startup

B Before handling a request

C Before pushing the request context

D After handling a request

Flask pops the application context after the request or CLI command finishes to clean up resources.

Which of these is true about Flask context lifecycle?

A Application context is pushed before request context

B Application context is popped before request context

C Request context is pushed before application context

D Contexts are never popped automatically

Flask pushes the application context first, then the request context, and pops them in reverse order.

How can you manually activate an application context in Flask?

A Using 'with app.app_context():'

B Using 'with app.request_context():'

C Using 'app.push_context()'

D Using 'app.activate_context()'

You manually activate the application context using 'with app.app_context():' to push it temporarily.

What happens if you try to access request data outside the request context?

A Flask returns default values

B Flask raises a RuntimeError

C Flask silently ignores the access

D Flask creates a new request context automatically

Accessing request data outside the request context raises a RuntimeError because the data is not available.

Describe the lifecycle of Flask contexts during a web request.

Think about the order of pushing and popping contexts around request handling.

Explain how you can manually manage Flask contexts in your code and why you might do that.

Consider situations outside normal request handling where context is needed.

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