DEBUG mode behavior in Django - Step-by-Step Execution

Concept Flow - DEBUG mode behavior

Start Django App

↓

Check DEBUG setting

↓

Handle requests

This flow shows how Django checks the DEBUG setting at startup and chooses detailed error pages and dev tools if True, or generic error pages if False.

Execution Sample

Django

DEBUG = True

# On error
if DEBUG:
    show_detailed_error()
else:
    show_generic_error()

This code decides which error page to show based on the DEBUG setting.

Execution Table

Step	DEBUG Value	Error Occurred?	Action Taken	Output
1	True	No	Serve normal page	Normal page shown
2	True	Yes	Show detailed error	Detailed error page with stack trace
3	False	No	Serve normal page	Normal page shown
4	False	Yes	Show generic error	Generic error page without details
5	True	Yes	Enable debug toolbar	Debug toolbar visible on page
6	False	Yes	Disable debug toolbar	No debug toolbar
7	-	-	-	Execution ends

💡 Execution ends after handling error or normal request based on DEBUG value.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	Final
DEBUG	True	True	True	False	False
Error Occurred	No	No	Yes	Yes	Yes
Action Taken	-	Serve normal page	Show detailed error	Show generic error	Show generic error
Output	-	Normal page shown	Detailed error page	Generic error page	Generic error page

Key Moments - 3 Insights

Why do I see a detailed error page only when DEBUG is True?

Because when DEBUG is True, Django shows detailed error pages with stack traces as shown in execution_table row 2. When False, it shows generic error pages (row 4) to avoid exposing sensitive info.

Does DEBUG affect normal page serving when no error occurs?

No, as seen in rows 1 and 3, normal pages are served regardless of DEBUG value if no error happens.

What happens to the debug toolbar when DEBUG is False?

The debug toolbar is disabled and not shown, as shown in row 6 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output at step 2 when DEBUG is True and an error occurs?

A Normal page shown

B Generic error page without details

C Detailed error page with stack trace

D Debug toolbar hidden

💡 Hint

Check the 'Output' column at step 2 in the execution_table.

At which step does Django disable the debug toolbar?

A Step 6

B Step 5

C Step 3

D Step 1

💡 Hint

Look for 'Disable debug toolbar' in the 'Action Taken' column.

If DEBUG is set to False, what will happen when an error occurs?

A Show detailed error page

B Show generic error page

C Show debug toolbar

D Serve normal page

💡 Hint

Refer to execution_table row 4 for DEBUG=False and error.

Concept Snapshot

DEBUG mode in Django controls error page detail.
Set DEBUG=True to see detailed errors and dev tools.
Set DEBUG=False for generic error pages in production.
DEBUG does not affect normal page serving.
Always disable DEBUG in live sites for security.

Full Transcript

Django uses the DEBUG setting to decide how to handle errors and developer tools. When DEBUG is True, detailed error pages with stack traces appear, and the debug toolbar is enabled. When False, Django shows generic error pages without sensitive info and disables developer tools. Normal pages serve the same regardless of DEBUG if no error occurs. This behavior helps developers during development and protects users in production.

Practice

1. What is the main purpose of setting DEBUG = True in a Django project?

easy

A. To enable database backups automatically

B. To improve website speed in production

C. To disable all logging

D. To show detailed error messages during development

Solution

1. Step 1: Understand the role of DEBUG in Django

   DEBUG mode is designed to help developers by showing detailed error messages and debugging information.

2. Step 2: Identify the correct purpose

   Setting DEBUG = True enables detailed error pages, which is useful only during development, not production.

3. Final Answer:

   To show detailed error messages during development -> Option D

4. Quick Check:

   DEBUG = True shows errors [OK]

Hint: DEBUG = True means show errors for fixing [OK]

Common Mistakes:

• Thinking DEBUG improves production speed
• Confusing DEBUG with logging settings
• Assuming DEBUG enables backups

2. Which of the following is the correct way to disable debug mode in Django's settings.py?

easy

A. DEBUG = False

B. DEBUG = 'False'

C. debug = False

D. DEBUG = 0

Solution

1. Step 1: Check the correct syntax for boolean in Python

   In Python, boolean values are capitalized: True or False without quotes.

2. Step 2: Identify the correct assignment in settings.py

   DEBUG must be assigned the boolean False, not a string or lowercase variable.

3. Final Answer:

   DEBUG = False -> Option A

4. Quick Check:

   Boolean False without quotes disables debug [OK]

Hint: Use capitalized False without quotes to disable debug [OK]

Common Mistakes:

• Using 'False' as a string instead of boolean
• Using lowercase debug variable
• Assigning numeric 0 instead of False

3. Given the following Django settings snippet:

DEBUG = True
ALLOWED_HOSTS = []

What will happen if you access the site from a browser?

medium

A. The site will redirect to a login page

B. The site will show a detailed error page if an error occurs

C. The site will run normally without errors

D. The site will block all hosts and show a 400 error

Solution

1. Step 1: Understand DEBUG and ALLOWED_HOSTS interaction

   When DEBUG is True, Django ignores ALLOWED_HOSTS restrictions and shows detailed errors.

2. Step 2: Predict behavior on error

   If an error occurs, Django will display a detailed debug page to help fix it.

3. Final Answer:

   The site will show a detailed error page if an error occurs -> Option B

4. Quick Check:

   DEBUG True shows detailed errors despite ALLOWED_HOSTS [OK]

Hint: DEBUG True overrides ALLOWED_HOSTS for errors [OK]

Common Mistakes:

• Thinking ALLOWED_HOSTS blocks access when DEBUG is True
• Assuming no error page shows
• Confusing error page with login redirect

4. You set DEBUG = False but still see detailed error pages in production. What is the most likely cause?

medium

A. DEBUG must be set to a string 'False'

B. You forgot to set ALLOWED_HOSTS properly

C. You need to restart the Django server

D. You need to clear browser cache

Solution

1. Step 1: Recall DEBUG False behavior

   When DEBUG is False, detailed error pages should not appear. If they do, the setting likely didn't take effect.

2. Step 2: Identify common mistake

   Changes to settings.py require restarting the Django server to reload the configuration.

3. Final Answer:

   You need to restart the Django server -> Option C

4. Quick Check:

   Restart server after settings changes [OK]

Hint: Restart Django server after changing DEBUG [OK]

Common Mistakes:

• Using string 'False' instead of boolean
• Not restarting server after changes
• Assuming browser cache causes error pages

5. You want to deploy your Django app safely. Which combination of settings is best practice for production?

hard

A. DEBUG = False and ALLOWED_HOSTS set to your domain names

B. DEBUG = False and ALLOWED_HOSTS = []

C. DEBUG = True and ALLOWED_HOSTS = ['*']

D. DEBUG = True and ALLOWED_HOSTS set to your domain names

Solution

1. Step 1: Understand production safety rules

   In production, DEBUG must be False to avoid exposing sensitive info.

2. Step 2: Set ALLOWED_HOSTS correctly

   ALLOWED_HOSTS must list your domain names to restrict access and prevent host header attacks.

3. Step 3: Evaluate options

   Only DEBUG = False with proper ALLOWED_HOSTS is safe for production.

4. Final Answer:

   DEBUG = False and ALLOWED_HOSTS set to your domain names -> Option A

5. Quick Check:

   Production needs DEBUG False + correct ALLOWED_HOSTS [OK]

Hint: Production: DEBUG False + real domains in ALLOWED_HOSTS [OK]

Common Mistakes:

• Leaving DEBUG True in production
• Using wildcard '*' in ALLOWED_HOSTS
• Leaving ALLOWED_HOSTS empty