Closed egasimus closed 10 years ago
Actually, setting DEBUG_TOOLBAR_PATCH_SETTINGS = False
in my settings file ostensibly fixed things. I already had debug_toolbar.middleware.DebugToolbarMiddleware
in my MIDDLEWARE_CLASSES
when patching was set to True
, however removing it didn't help. So this apparently has to do with the patcher itself.
Yes, the automatic patcher doesn't work well in projects that have some form of autodiscovery. You have to use the explicit setup, as explained in the documentation.
Building a custom CMS with Django 1.6.1. After updating to django-debug-toolbar 1.0.1, I started getting a strange error when trying to run
syncdb
,migrate
orschemamigration
(probably some others as well); but not when importing stuff fromshell
.Removing django-debug-toolbar from
INSTALLED_APPS
fixed the issue, and so did reverting to v0.11.0. Installing django-debug-toolbar 1.0.1 from scratch (i.e. re-initializing my development VM from scratch) didn't help; in fact, that was when I found out there's something wrong.Judging from the import trace (
python -v
), the culprit is theredirects
panel; I have a reference to a customAdminSite
in myurls.py
, and thatAdminSite
uses custom django-authority permissions extensively. However, something that the redirects panel is doing seems to cause a circular import.Stack trace:
_List of installed apps:_
Import trail (output of python -v, extra comments removed for clarity)