o QDi+@sddlZddlZddlmZddlmZddlmZmZm Z ddl m Z ddl m Z mZddlmZddlmZdd lmZmZdd lmZGd d d eZd dZddZe ddZe ddZddZe ddZe ddZ e ddZ!e ddZ"dS)N) AppConfig)settings)ErrorWarningregister)GZipMiddleware)NoReverseMatchreverse) import_string) gettext_lazy)APP_NAMEr)CONFIG_DEFAULTScs0eZdZdZedZddZfddZZS)DebugToolbarConfig debug_toolbarz Debug ToolbarcCs0ddlm}|D]}|q t|jdS)Nr DebugToolbar)debug_toolbar.toolbarrget_panel_classesready_manage_migrations_visibilityname)selfrclsrK/var/www/Datamplify/venv/lib/python3.10/site-packages/debug_toolbar/apps.pyrs   zDebugToolbarConfig.readycs(t}|ddkrtSi|_dS)a Override import models to avoid allowing users to dynamically fetch a model that doesn't have a table behind it unless they are using the DatabaseStore. This also prevents the command `migrate --run-syncdb` from creating tables for the models. TOOLBAR_STORE_CLASS!debug_toolbar.store.DatabaseStoreN) dt_settings get_configsuper import_modelsmodels)r dt_config __class__rrr s   z DebugToolbarConfig.import_models) __name__ __module__ __qualname__r_ verbose_namerr __classcell__rrr#rrs  rcCs&tddkrtj|ddSdS)z Adjust the toolbar's migration visibility by manipulating the project's settings. This is a hack since it's manipulating settings. rrN)rrrMIGRATION_MODULES setdefault)app_namerrrr+s rcsTfdd|dd}|didd}|rt|}|dup%d|v}|p)|S) a Checks if a template configuration is valid. The toolbar requires either the toolbars to be unspecified or ``django.template.loaders.app_directories.Loader`` to be included in the loaders. If custom loaders are specified, then APP_DIRS must be True. c3s>|D]}t|tr|dV|dEdHq|VqdS)z Recursively flatten the settings list of template loaders. Check for (loader, [child_loaders]) tuples. Django's default cached loader uses this pattern. rN) isinstancetuple)loadersloader flat_loadersrrr4Ds  z+check_template_config..flat_loadersAPP_DIRSFOPTIONSr1Nz.django.template.loaders.app_directories.Loader)getlist)configapp_dirsr1has_app_loadersrr3rcheck_template_config:s  r<cKsddlm}g}d}g}tddtjDr |tddddtd r1|td d d d|Sttj D]\}}t t |rB|}q6t ||rL||q6|s[|td ddd|St |dkrm|tdddd|S|dur|d|kr|tdddd|S)Nr)DebugToolbarMiddlewarecss|]}t| VqdSN)r<).0r9rrr fsz#check_middleware..zAt least one DjangoTemplates TEMPLATES configuration needs to use django.template.loaders.app_directories.Loader or have APP_DIRS set to True.zInclude django.template.loaders.app_directories.Loader in ["OPTIONS"]["loaders"]. Alternatively use APP_DIRS=True for at least one django.template.backends.django.DjangoTemplates backend configuration.zdebug_toolbar.W006hintidMIDDLEWARE_CLASSESz>debug_toolbar is incompatible with MIDDLEWARE_CLASSES setting.z,Use MIDDLEWARE instead of MIDDLEWARE_CLASSESzdebug_toolbar.W004zKdebug_toolbar.middleware.DebugToolbarMiddleware is missing from MIDDLEWARE.zBAdd debug_toolbar.middleware.DebugToolbarMiddleware to MIDDLEWARE.zdebug_toolbar.W001r.zTdebug_toolbar.middleware.DebugToolbarMiddleware occurs multiple times in MIDDLEWARE.zMLoad debug_toolbar.middleware.DebugToolbarMiddleware only once in MIDDLEWARE.zdebug_toolbar.W002zrdebug_toolbar.middleware.DebugToolbarMiddleware occurs before django.middleware.gzip.GZipMiddleware in MIDDLEWARE.zrMove debug_toolbar.middleware.DebugToolbarMiddleware to after django.middleware.gzip.GZipMiddleware in MIDDLEWARE.zdebug_toolbar.W003) debug_toolbar.middlewarer=allr TEMPLATESappendr is_overridden enumerate MIDDLEWAREis_middleware_classrlen) app_configskwargsr=errors gzip_indexdebug_toolbar_indexesi middlewarerrrcheck_middleware^sl       rUcKs:ddlm}g}|D]}|D]}||qq |S)zOAllow each panel to check the toolbar's integration for their its own purposes.rr)rrr run_checksrH)rNrOrrP panel_class check_messagerrrcheck_panel_configss    rYcCs6zt|}Wn tyYdSwt|ot||Sr>)r ImportErrorinspectisclass issubclass)middleware_classmiddleware_pathmiddleware_clsrrrrLs   rLcKs(g}t}|s|tdddd|S)Nz&Setting DEBUG_TOOLBAR_PANELS is empty.zASet DEBUG_TOOLBAR_PANELS to a non-empty list in your settings.py.zdebug_toolbar.W005rA)r get_panelsrHr)rNrOrPpanelsrrr check_panelssrccKs6ddh}ttd| }|rtddddgSgS)zP Check that JavaScript files are resolving to the correct content type. zapplication/javascriptztext/javascriptz toolbar.jsz9JavaScript files are resolving to the wrong content type.aThe Django Debug Toolbar may not load properly while mimetypes are misconfigured. See the Django documentation for an explanation of why this occurs. https://docs.djangoproject.com/en/stable/ref/contrib/staticfiles/#static-file-development-view This typically occurs on Windows machines. The suggested solution is to modify HKEY_CLASSES_ROOT in the registry to specify the content type for JavaScript files. [HKEY_CLASSES_ROOT\.js] "Content Type"="application/javascript"zdebug_toolbar.W007rA)set mimetypes guess_type intersectionr)rNrOjavascript_types check_failedrrrjs_mimetype_checks rjcKsvtdtdk}z ttdd}Wn ty d}Ynw|o%| }tjs9tdr9|r9tdddd gSgS) zI Check that the toolbar is not being used when tests are running SHOW_TOOLBAR_CALLBACKz :render_panelTFIS_RUNNING_TESTSz1The Django Debug Toolbar can't be used with testsaRDjango changes the DEBUG setting to False when running tests. By default the Django Debug Toolbar is installed because DEBUG is set to True. For most cases, you need to avoid installing the toolbar when running tests. If you feel this check is in error, you can set `DEBUG_TOOLBAR_CONFIG['IS_RUNNING_TESTS'] = False` to bypass this check.zdebug_toolbar.E001rA) rrr r r rrDEBUGr)rNrOshow_toolbar_changedtoolbar_urls_installedlikely_error_setuprrr0debug_toolbar_installed_when_running_tests_checks0     rqcKs0g}ttdi}d|vr|tdddd|S)NDEBUG_TOOLBAR_CONFIGOBSERVE_REQUEST_CALLBACKzSThe deprecated OBSERVE_REQUEST_CALLBACK setting is present in DEBUG_TOOLBAR_CONFIG.zFUse the UPDATE_ON_FETCH and/or SHOW_TOOLBAR_CALLBACK settings instead.zdebug_toolbar.W008rA)getattrrrHr)rNrOrP USER_CONFIGrrrcheck_settings"s rv)#r[re django.appsr django.confrdjango.core.checksrrrdjango.middleware.gzipr django.urlsrr django.utils.module_loadingr django.utils.translationr r(rr rdebug_toolbar.settingsr rrr<rUrYrLrcrjrqrvrrrrs6      $ N     /