django-plugin-django-debug-toolbar
Django plugin that installs and configures the Django Debug Toolbar
Goal
The Django Debug Toolbar is amazingly useful for development. It's so powerful that it's very dangerous to activate it in production.
The goal of this plugin is to enable a developer to activate the Django Debug Toolbar with the minimum number of steps, while keeping debug related code out of the codebase.
Installation
First configure your Django project to use DJP.
Then install this plugin in the same environment as your Django application.
pip install django-plugin-django-debug-toolbar
Usage
Looking at Django Debug Toolbar's installation instructions, this plugin takes care of the following steps (using their numbering):
- #1. Install the Package
- #2. Check for Prerequisites
- setup
django.contrib.staticfiles
- setup
- #3. Install the App
- #4. Add the URLs
- #5. Add the Middleware
- #6. Configure Internal IPs
- to include
127.0.0.1
- to include
But you still need to:
- #2. Check for Prerequisites
- like settings for templates
- #6. Configure Internal IPs
- if you require IPs other than
127.0.0.1, set them inINTERNAL_IPSin your settings
- if you require IPs other than
- #7. Disable the toolbar when running tests (optional)
- perhaps do this by disabling DJP when testing
Middleware ordering
This plugin injects the Debug Toolbar Middleware early, but not too early, in the middleware list.
It needs to run after any midddleware that decodes requests (GZipMiddleware), or sets request.META['REMOTE_ADDR'] (like django-xforwardedfor-middleware or django-xff).
If you have any other middleware that needs to run before the Debug Toolbar Middleware, please open a ticket and we'll add it to the TOOLBAR_MUST_GO_AFTER list.
Development
To set up this plugin locally, first checkout the code. Then create a new virtual environment:
cd django-plugin-django-debug-toolbar
python -m venv venv
source venv/bin/activate
Now install the dependencies and test dependencies:
pip install -e '.[test]'
To run the tests:
python -m pytest
Metadata
Release files for django-plugin-django-debug-toolbar 0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_plugin_django_debug_toolbar-0.5.2.tar.gz | 2.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_plugin_django_debug_toolbar-0.5.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.8 kB
Release files / django_plugin_django_debug_toolbar-0.5.2.tar.gz
| Download URL | django_plugin_django_debug_toolbar-0.5.2.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2dd88b60930d41e0aaa324cd1f3e9c22d638de47082e347b746c9afa81581c09
|
|
BLAKE2b-256 checksum How to use checksums |
63b2f9b4b23ca374b6f36ebc55fba42fe9f1a0a8c3dd1437734b7d9b64e049d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2025.
Transparency logRelease files / django_plugin_django_debug_toolbar-0.5.2-py3-none-any.whl
| Download URL | django_plugin_django_debug_toolbar-0.5.2-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6efed5da5feb1b82e8e661711845e58877f2f841d6d29b0d292decbbe6e3bf0d
|
|
BLAKE2b-256 checksum How to use checksums |
6dc600b199d7c79a43cb63dd1a4645b0db3cdf24bfd8817bbc3a5eb43b6a6356
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2025.
Transparency log