Why Flask contexts matter - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Flask class correctly.

Flask

from flask import [1]
app = [1](__name__)

Drag options to blanks, or click blank then click option'

Arender_template

BRequest

CBlueprint

DFlask

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Request instead of Flask

Using render_template where Flask is needed

Forgetting to import Flask

The Flask class is imported from the flask package to create the app instance.

2fill in blank

medium

Complete the code to access the current request object inside a view function.

Flask

from flask import Flask, [1]

app = Flask(__name__)

@app.route('/')
def home():
    user_agent = [1].headers.get('User-Agent')
    return f"Your agent is {user_agent}"

Drag options to blanks, or click blank then click option'

Arequest

Bsession

Cg

Durl_for

Attempts:

3 left

💡 Hint

Common Mistakes

Using session instead of request

Trying to access request without importing it

Confusing g with request

The request object gives access to details about the current HTTP request.

3fill in blank

hard

Fix the error in accessing the Flask application context variable.

Flask

from flask import Flask, current_app

app = Flask(__name__)

with app.[1]():
    print('App name:', current_app.name)

Drag options to blanks, or click blank then click option'

Arequest

Bapp_context

Ccurrent_app

Dsession

Attempts:

3 left

💡 Hint

Common Mistakes

Using request instead of app_context

Trying to use current_app without context

Not creating any context before accessing app.name

The app_context() method creates the application context needed to access app variables safely.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that stores request header lengths only if the header exists.

Flask

from flask import request

header_lengths = {header: len(request.headers.get(header)) for header in ['User-Agent', 'Host'] if request.headers.get([1]) [2] None}

Drag options to blanks, or click blank then click option'

A'User-Agent'

B==

C!=

Dheader

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '!=' in the condition

Using a header name not in the list

Not checking if header exists before len()

We check if the header exists by comparing it to None with '!=' before getting its length.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that stores uppercase header names and their values if the value length is greater than 5.

Flask

from flask import request

filtered_headers = [1]: [2] for [3], [2] in request.headers.items() if len([2]) > 5

Drag options to blanks, or click blank then click option'

Aheader.upper()

Bheader

Cvalue

Drequest.headers

Attempts:

3 left

💡 Hint

Common Mistakes

Using request.headers directly as key or value

Not using .upper() for keys

Mixing variable names in comprehension

The comprehension uses header.upper() as keys, header as the variable for keys, and value as the variable for values.

Practice

1. Why does Flask use contexts like the application context and request context?

easy

A. To speed up the server by caching all data globally

B. To keep data for each user and request separate and organized

C. To allow Flask to run without a web server

D. To store all data permanently in memory

Solution

1. Step 1: Understand Flask's need for data separation

   Flask handles many users and requests at once, so it must keep their data separate to avoid mixing information.

2. Step 2: Role of contexts

   Application and request contexts help Flask organize data specific to the app or each request, keeping them isolated.

3. Final Answer:

   To keep data for each user and request separate and organized -> Option B

4. Quick Check:

   Contexts separate data = B [OK]

Hint: Contexts isolate user/request data to avoid mix-ups [OK]

Common Mistakes:

• Thinking contexts speed up the server by caching globally
• Believing Flask can run without a web server due to contexts
• Assuming contexts store data permanently in memory

2. Which of the following is the correct way to push an application context in Flask?

easy

A. app.app_context().push()

B. app.push_context()

C. push.app_context()

D. app.context_push()

Solution

1. Step 1: Recall Flask application context syntax

   The correct method to push an application context is calling app.app_context() which returns a context object.

2. Step 2: Push the context

   Calling push() on that context object activates it, so the full syntax is app.app_context().push().

3. Final Answer:

   app.app_context().push() -> Option A

4. Quick Check:

   Correct context push syntax = A [OK]

Hint: Use app.app_context().push() to activate app context [OK]

Common Mistakes:

• Using incorrect method names like push_context or context_push
• Calling push() directly on app instead of context object
• Mixing order of method calls

3. Consider this Flask code snippet inside a request handler:

from flask import request

def handler():
    user_agent = request.headers.get('User-Agent')
    return f"Agent: {user_agent}"

What will happen if you try to access request.headers outside a request context?

medium

A. It returns the last request's headers

B. It returns None without error

C. It returns an empty dictionary

D. It raises a RuntimeError about working outside request context

Solution

1. Step 1: Understand request context role

   The request object is only available during an active request context, which Flask manages automatically during a web request.

2. Step 2: Accessing request outside context

   If you try to access request.headers outside this context, Flask raises a RuntimeError warning you are working outside the request context.

3. Final Answer:

   It raises a RuntimeError about working outside request context -> Option D

4. Quick Check:

   Request outside context = A [OK]

Hint: Access request only inside request context to avoid errors [OK]

Common Mistakes:

• Expecting None or empty dict instead of error
• Assuming request keeps last request data globally
• Not knowing request object needs active context

4. You wrote this Flask code but get a RuntimeError: "Working outside of application context." What is the likely fix?

from flask import current_app

def get_config():
    return current_app.config['DEBUG']

print(get_config())

medium

A. Wrap the call to get_config() inside app.app_context()

B. Replace current_app with app directly

C. Import Flask instead of current_app

D. Remove the print statement

Solution

1. Step 1: Identify cause of error

   The error means current_app is accessed without an active application context.

2. Step 2: Fix by pushing app context

   Wrapping the call inside with app.app_context(): or manually pushing the context activates current_app.

3. Final Answer:

   Wrap the call to get_config() inside app.app_context() -> Option A

4. Quick Check:

   App context needed for current_app = D [OK]

Hint: Use app.app_context() to access current_app safely [OK]

Common Mistakes:

• Trying to replace current_app with app without context
• Thinking importing Flask fixes context errors
• Ignoring the need for context when printing config

5. You want to store user-specific data during a request without passing it explicitly between functions. Which Flask context is best to use and why?

from flask import g

def set_user_data(data):
    g.user_data = data

def get_user_data():
    return getattr(g, 'user_data', None)

hard

A. Use a global variable outside Flask contexts

B. Use the application context because it stores global app data

C. Use the request context because it is unique per request and stores temporary data

D. Use session cookies to store temporary data

Solution

1. Step 1: Understand purpose of Flask's g object

   The g object is part of the request context and is designed to store data during a single request.

2. Step 2: Why request context fits best

   Request context is unique per user request, so data stored in g stays isolated and temporary, perfect for user-specific data.

3. Final Answer:

   Use the request context because it is unique per request and stores temporary data -> Option C

4. Quick Check:

   Request context for user data = C [OK]

Hint: Use request context's g for per-request temporary data [OK]

Common Mistakes:

• Confusing application context as place for user data
• Using global variables causing data mix between users
• Thinking session cookies replace request context storage