Development server with debug mode in Flask - Step-by-Step Execution

Concept Flow - Development server with debug mode

Start Flask app

↓

Check debug mode setting

Yes↓

Enable debug features

↓

Run development server

↓

Detect code changes?

Yes→Reload server

No↓

Wait for requests

↓

Handle requests with debug info

↓

Repeat

The Flask app starts, checks if debug mode is on, enables debug features, runs the server, reloads on code changes, and shows debug info on errors.

Execution Sample

Flask

from flask import Flask
app = Flask(__name__)

app.run(debug=True)

Starts a Flask development server with debug mode enabled to auto-reload and show detailed errors.

Execution Table

Step	Action	Debug Mode?	Result	Server State
1	Start Flask app	N/A	App instance created	Not running
2	Call app.run(debug=True)	True	Debug features enabled	Starting server
3	Server listens for requests	True	Auto-reload active	Running
4	Code change detected	True	Server reloads automatically	Restarting
5	Error occurs during request	True	Show detailed debug traceback	Running
6	No code change, handle request	True	Serve response normally	Running
7	Stop server	True	Server stops	Stopped

💡 Server stops when manually terminated or error is fatal

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 7
debug	False (default)	True	True	N/A
server_state	Not running	Starting server	Restarting	Stopped

Key Moments - 3 Insights

Why does the server reload automatically when I change my code?

Because debug=True turns on the auto-reload feature, as shown in step 4 of the execution_table where code changes trigger a server restart.

What happens if I set debug=False?

The server runs without debug features: no auto-reload and no detailed error pages. This is implied by the debug mode check in step 2.

Does the debug mode affect how errors are shown?

Yes, with debug=True, errors show detailed tracebacks in the browser (step 5), helping you fix bugs quickly.

Visual Quiz - 3 Questions

Look at the execution_table, what is the server state after step 4?

A Restarting

B Stopped

C Running

D Starting server

💡 Hint

Check the 'Server State' column for step 4 in the execution_table.

At which step does the server show detailed debug tracebacks?

A Step 3

B Step 5

C Step 6

D Step 7

💡 Hint

Look for 'Show detailed debug traceback' in the 'Result' column.

If debug=False, which behavior would NOT happen?

A Server shows detailed error pages

B Server starts and listens for requests

C Server auto-reloads on code changes

D Server stops when manually terminated

💡 Hint

Refer to the 'Debug Mode?' column and what debug=True enables in the execution_table.

Concept Snapshot

Flask development server with debug mode:
- Use app.run(debug=True) to enable debug mode
- Debug mode auto-reloads server on code changes
- Shows detailed error tracebacks in browser
- Helps rapid development and debugging
- Not for production use

Full Transcript

This visual trace shows how Flask runs a development server with debug mode enabled. When you start the app with app.run(debug=True), Flask enables features like auto-reloading the server when you change code and showing detailed error messages in the browser. The execution table walks through starting the app, enabling debug, listening for requests, detecting code changes to reload, handling errors with debug info, and stopping the server. Variables like debug and server_state change as the server runs. Key moments clarify why auto-reload happens and how debug mode affects error display. The quiz tests understanding of server states and debug features. This helps beginners see how debug mode improves development experience by making code changes instantly visible and errors easier to fix.

Practice

1. What does setting debug=True in app.run() do in a Flask app?

easy

A. It hides all error messages from the user.

B. It disables the server from running.

C. It makes the app run faster in production.

D. It shows detailed error messages and reloads the server on code changes.

Solution

1. Step 1: Understand debug mode purpose

   Debug mode helps developers by showing detailed error messages and automatically restarting the server when code changes.

2. Step 2: Check what debug=True does in app.run()

   Passing debug=True enables this helpful behavior during development.

3. Final Answer:

   It shows detailed error messages and reloads the server on code changes. -> Option D

4. Quick Check:

   Debug mode = detailed errors + auto reload [OK]

Hint: Debug mode shows errors and reloads automatically [OK]

Common Mistakes:

• Thinking debug mode speeds up production
• Believing debug mode hides errors
• Confusing debug mode with disabling the server

2. Which of the following is the correct way to start a Flask development server with debug mode enabled?

easy

A. app.run(debug=True)

B. app.run(debug=1)

C. app.run(mode='debug')

D. app.run(enable_debug=True)

Solution

1. Step 1: Recall Flask run method parameters

   The app.run() method accepts a debug parameter as a boolean to enable debug mode.

2. Step 2: Identify correct syntax

   Using app.run(debug=True) is the standard and correct way to enable debug mode.

3. Final Answer:

   app.run(debug=True) -> Option A

4. Quick Check:

   Correct debug syntax = debug=True [OK]

Hint: Use debug=True exactly in app.run() [OK]

Common Mistakes:

• Using incorrect parameter names like mode or enable_debug
• Passing debug as a string or number instead of boolean
• Confusing debug with other run parameters

3. What will happen when you run this Flask code?

from flask import Flask
app = Flask(__name__)

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

if __name__ == '__main__':
    app.run(debug=True)

medium

A. The server will not start because the route is missing a template.

B. The server starts but debug mode is off, so no error details are shown.

C. The server starts with debug mode, showing errors and auto-reloading on code changes.

D. The code will raise a syntax error because debug=True is invalid here.

Solution

1. Step 1: Analyze the code structure

   The code defines a Flask app with a simple route returning 'Hello!'. The server is started with debug=True.

2. Step 2: Understand effect of debug=True

   Passing debug=True enables debug mode, so errors show detailed info and the server reloads on code changes.

3. Final Answer:

   The server starts with debug mode, showing errors and auto-reloading on code changes. -> Option C

4. Quick Check:

   app.run(debug=True) = debug mode active [OK]

Hint: debug=True means errors show and server reloads [OK]

Common Mistakes:

• Thinking debug=True causes syntax errors
• Assuming debug mode is off by default
• Believing routes need templates to start server

4. You wrote this code but the Flask server does not reload on code changes:

from flask import Flask
app = Flask(__name__)

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

if __name__ == '__main__':
    app.run()

What is the likely fix?

medium

A. Change app = Flask(__name__) to app = Flask().

B. Add debug=True to app.run() to enable auto-reload.

C. Add reload=True parameter to app.run().

D. Remove the if __name__ == '__main__' guard.

Solution

1. Step 1: Identify missing debug mode

   The code calls app.run() without debug=True, so debug mode and auto-reload are off.

2. Step 2: Enable debug mode for auto-reload

   Adding debug=True to app.run() activates debug mode, enabling error messages and auto-reload on code changes.

3. Final Answer:

   Add debug=True to app.run() to enable auto-reload. -> Option B

4. Quick Check:

   Missing debug=True disables auto-reload [OK]

Hint: Add debug=True to app.run() for auto-reload [OK]

Common Mistakes:

• Trying to use reload=True which is invalid
• Removing the main guard which is unrelated
• Changing Flask app initialization unnecessarily

5. You want to run your Flask app with debug mode but only on your local machine, not in production. Which code snippet correctly achieves this?

hard

A. if __name__ == '__main__':
app.run(debug=True)

B. app.run(debug=True) # runs debug mode always

C. if __name__ == '__main__':
app.run() # debug mode off

D. app.run() # debug mode on by default

Solution

1. Step 1: Understand the main guard usage

   The if __name__ == '__main__' block ensures the server runs only when the script is executed directly, typically local development.

2. Step 2: Enable debug mode only inside main guard

   Placing app.run(debug=True) inside this block enables debug mode only locally, avoiding debug mode in production.

3. Step 3: Check other options

   Running app.run(debug=True) outside the guard runs debug mode always, which is unsafe for production.

4. Final Answer:

   if __name__ == '__main__': app.run(debug=True) -> Option A

5. Quick Check:

   Main guard + debug=True = safe local debug [OK]

Hint: Use main guard with debug=True for local only [OK]

Common Mistakes:

• Running debug mode outside main guard risks production
• Assuming debug mode is off by default
• Not using main guard and causing unwanted server start