Debug mode error pages in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of Flask's debug mode error pages?

Flask's debug mode error pages help developers by showing detailed error information and a traceback when an error happens during development. This makes it easier to find and fix bugs.

beginner

How do you enable debug mode in a Flask application?

You enable debug mode by setting app.debug = True or by running the app with app.run(debug=True). This activates detailed error pages and auto-reloading.

intermediate

What information does Flask's debug error page show when an exception occurs?

It shows the error type, message, a full traceback of the error, and interactive tools like the debugger console to inspect variables at the error point.

intermediate

Why should debug mode never be enabled in a production Flask app?

Because debug mode exposes detailed error information and an interactive debugger that can be a security risk. It can reveal sensitive data and allow code execution by attackers.

advanced

What happens if you try to access a Flask app's debug error page from a remote machine?

By default, Flask only shows the debug error page on localhost for security. Remote access to the debugger is blocked unless explicitly allowed, which is unsafe.

How do you activate debug mode in Flask?

A app.start(debug=False)

B app.run(production=True)

C app.debug = False

D app.run(debug=True)

Use app.run(debug=True) to enable debug mode and see detailed error pages.

What does Flask's debug error page NOT show?

A Full error traceback

B Interactive debugger console

C User's browser history

D Error type and message

Flask's debug page shows error details but does not show the user's browser history.

Why is it unsafe to run Flask with debug mode enabled in production?

A It exposes sensitive error details and allows code execution

B It hides error messages

C It disables logging

D It slows down the app

Debug mode exposes sensitive info and an interactive debugger that attackers could misuse.

What is the default behavior of Flask debug error pages regarding remote access?

A Accessible from any IP

B Only accessible from localhost

C Disabled completely

D Requires a password

By default, debug error pages are only shown on localhost to protect security.

Which of these is a feature of Flask's debug error page?

A Interactive traceback with variable inspection

B Auto-correcting code errors

C Automatic deployment

D User authentication

Flask's debug page lets you inspect variables at the error point interactively.

Explain how Flask's debug mode error pages help during development and why they should be disabled in production.

Think about what info the error page shows and who should see it.

Describe the steps to enable debug mode in a Flask app and what happens when an error occurs while debug mode is on.

Focus on configuration and error page behavior.

Practice

1. What does enabling debug mode in a Flask app do?

easy

A. Disables all error messages

B. Automatically fixes bugs in the code

C. Shows detailed error pages with debugging information

D. Prevents the app from restarting on code changes

Solution

1. Step 1: Understand debug mode purpose

   Debug mode helps developers by showing detailed error pages when something goes wrong.

2. Step 2: Compare options with debug mode behavior

   Only Shows detailed error pages with debugging information correctly describes that debug mode shows detailed error pages with debugging info.

3. Final Answer:

   Shows detailed error pages with debugging information -> Option C

4. Quick Check:

   Debug mode = detailed error pages [OK]

Hint: Debug mode shows detailed errors, not hides them [OK]

Common Mistakes:

• Thinking debug mode hides errors
• Believing debug mode fixes bugs automatically
• Confusing debug mode with production mode

2. Which of the following is the correct way to enable debug mode in Flask?

easy

A. app.run(debug=False)

B. app.debug = True

C. app.debug = False

D. app.config['DEBUG'] = False

Solution

1. Step 1: Recall how to enable debug mode

   Debug mode can be enabled by setting app.debug = True or app.config['DEBUG'] = True.

2. Step 2: Identify the correct option

   Only app.debug = True sets debug mode to True correctly.

3. Final Answer:

   app.debug = True -> Option B

4. Quick Check:

   Enable debug = app.debug = True [OK]

Hint: Set app.debug = True to enable debug mode [OK]

Common Mistakes:

• Setting debug to False instead of True
• Confusing app.run debug argument with app.debug property
• Using incorrect config keys

3. Given this Flask code snippet, what will you see if an error occurs?

from flask import Flask
app = Flask(__name__)
app.debug = True

@app.route('/')
def home():
    return 1 / 0  # This will cause an error

app.run()

medium

A. A detailed error page showing the division by zero traceback

B. A blank page with no error message

C. A generic 500 Internal Server Error page without details

D. The app will crash and stop running

Solution

1. Step 1: Analyze debug mode effect on errors

   With app.debug = True, Flask shows detailed error pages including tracebacks.

2. Step 2: Understand the error in the code

   The route causes a division by zero error, triggering the debug error page.

3. Final Answer:

   A detailed error page showing the division by zero traceback -> Option A

4. Quick Check:

   Debug mode shows detailed error page on exceptions [OK]

Hint: Debug True shows detailed error pages on exceptions [OK]

Common Mistakes:

• Expecting a generic error page in debug mode
• Thinking the app crashes completely
• Assuming no error message is shown

4. What is wrong with this Flask app code if you want to see debug error pages?

from flask import Flask
app = Flask(__name__)
app.config['DEBUG'] = False

@app.route('/')
def index():
    return 1 / 0

app.run()

medium

A. Flask apps cannot handle division by zero errors

B. The route function is missing a return statement

C. app.run() is missing the debug=True argument

D. Debug mode is disabled, so detailed error pages won't show

Solution

1. Step 1: Check debug mode setting

   The code sets app.config['DEBUG'] = False, which disables debug mode.

2. Step 2: Understand effect on error pages

   With debug disabled, Flask shows generic error pages, not detailed ones.

3. Final Answer:

   Debug mode is disabled, so detailed error pages won't show -> Option D

4. Quick Check:

   Debug False = no detailed error pages [OK]

Hint: Check if debug is True to get detailed error pages [OK]

Common Mistakes:

• Thinking app.run() debug argument is required if app.config['DEBUG'] is set
• Believing Flask cannot handle division by zero
• Confusing missing return with debug mode issues

5. You want to enable debug mode only during development but disable it in production. Which approach is best?

import os
from flask import Flask
app = Flask(__name__)

if os.getenv('FLASK_ENV') == 'development':
    app.debug = True
else:
    app.debug = False

@app.route('/')
def home():
    return 'Hello!'

app.run()

hard

A. Use environment variable to toggle debug mode as shown

B. Always set app.debug = True regardless of environment

C. Set app.debug = False and never change it

D. Remove app.debug and rely on app.run(debug=True)

Solution

1. Step 1: Understand environment-based debug control

   Using an environment variable like FLASK_ENV to toggle debug mode is a common and safe practice.

2. Step 2: Evaluate the code logic

   The code sets debug True only if environment is 'development', otherwise disables it, which is correct.

3. Final Answer:

   Use environment variable to toggle debug mode as shown -> Option A

4. Quick Check:

   Env variable controls debug mode safely [OK]

Hint: Use env vars to enable debug only in development [OK]

Common Mistakes:

• Leaving debug always on in production
• Not using environment variables for config
• Relying only on app.run debug argument