No debug tracing using Django setting Debug = True

Question

During development I had DEBUG = True and I got debug tracings. Then I switched to DEBUG = False for testing the 404 / 500 pages.

Now, after I switched back to DEBUG = True I get no tracings, only "Internal Server Error" message.

How do I get those debug tracings back?

Thanks Martin Weberg

if you are running apache for example, you will need to reload it to see the changes in source code. — Uku Loskit
– Uku Loskit, Commented Sep 16, 2011 at 9:48
What is your server config like? (apache, nginx, etc?) or are you just using the built-in runserver? Either way you'll need to stop your server and start it again. I had an issue with using a restart command instead of stop/start and code in the settings.py was not updating — j_syk
– j_syk, Commented Sep 16, 2011 at 21:15
Sorry all of you... I did a search for "debug = False" in my projects folder and found it a second time further down in the settings.py file. Thank you all for the time you spent... — Martin Weberg
– Martin Weberg, Commented Sep 19, 2011 at 11:44

mtnpaul · Accepted Answer · 2019-09-13 13:34:20Z

3

How are you checking that DEBUG is set to True? Try

python manage.py shell

At the python prompt enter

from django.conf import settings

settings.DEBUG

what is the result?

If it is False then Debug maybe getting reset in perhaps a local_settings.py file (or some other place). Then do a grep -r "DEBUG = False" * from the project directory.

If the result for settings.DEBUG was True, then either apache is loading the wrong wsgi, or wsgi is loading the wrong settings.py file.

Which settings.py file is wsgi using?

edited Sep 13, 2019 at 13:34

answered Sep 17, 2011 at 21:27

mtnpaul

7044 silver badges13 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Martin Weberg Over a year ago

I found a second "debug = False" further down in the settings.py .... Thank you for pushing me in the right direction.

Chemary Over a year ago

import settings is not the good way to import settings, use instead from django.conf import settings

Ravi Kumar · Accepted Answer · 2017-03-13 08:45:41Z

1

first check DEBUG setting from

$ python manage.py shell
In [1]: from django.conf import settings

In [2]: settings.DEBUG
Out[2]: True

django.conf.settings abstracts the concepts of default settings and site-specific settings; it presents a single interface. It also decouples the code that uses settings from the location of your settings. Docs

answered Mar 13, 2017 at 8:45

Ravi Kumar

1,8073 gold badges22 silver badges31 bronze badges

Comments

szaman · Accepted Answer · 2011-09-16 11:01:48Z

0

try to enter invalid path. If 404.html will apear it means that somewhere DEBUG is still set to False, or like Uku Loskit wrote you have to reload server

EDIT:

Run django built-in server and see the results
print DEBUG at the end of settings.py

edited Sep 16, 2011 at 11:01

answered Sep 16, 2011 at 9:56

szaman

6,78414 gold badges57 silver badges81 bronze badges

1 Comment

Martin Weberg Over a year ago

Now I double checked. DEBUG = True I restarted Apache. Now when I enter an invalid URL i get the 404.html message. Ideas?

juankysmith · Accepted Answer · 2011-09-16 11:31:38Z

0

Give a chance to The Python Debugger, it is really simple, just import it and write pdb.set_trace() in the line you want to start debugging.

answered Sep 16, 2011 at 11:31

juankysmith

12.5k6 gold badges39 silver badges65 bronze badges

Comments

infrared · Accepted Answer · 2011-09-17 21:31:29Z

0

You can check the DEBUG setting by doing:

python manage.py shell
import settings
print settings.DEBUG

answered Sep 17, 2011 at 21:31

infrared

3,6262 gold badges27 silver badges37 bronze badges

Comments

Rob · Accepted Answer · 2020-07-13 17:45:55Z

0

If you have verified DEBUG is True at runtime and this is still happening, ensure you have not set DEBUG_PROPAGATE_EXCEPTIONS This setting will cause you to not see debug tracebacks in the browser.

answered Jul 13, 2020 at 17:45

Rob

1,9892 gold badges21 silver badges34 bronze badges

Collectives™ on Stack Overflow

No debug tracing using Django setting Debug = True

6 Answers 6

2 Comments

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

2 Comments

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related