The application context in Flask keeps data related to the app, such as configuration and database connections, separate from request-specific data. This helps Flask know what app is running when code executes outside a request.
request outside a request context?flask.request.method outside any route or request handler. What will happen?from flask import request print(request.method)
Accessing request outside a request context causes Flask to raise a RuntimeError because it cannot find the current request data.
The application context is pushed first because it is broader and holds app-level data. Then the request context is pushed for request-specific data. After the view runs, Flask pops the request context, then the application context.
Option A correctly creates and pushes the application context, then creates and pushes the request context. Option A uses context managers but does not push manually. Options A and B use invalid method orders or non-existent methods.
from flask import Flask, request app = Flask(__name__) @app.route('/') def index(): return f"Method: {request.method}" print(request.method)
The print statement runs when the script loads, outside any HTTP request. Flask raises RuntimeError because request data is only available during an active request context.