Welcome to the django-removals - a maintainer's best friend for finding removed features in your Django project
PyPI • GitHub • Full documentation
Creator & Maintainer: Beyonder Deutschland
Features
This package will throw Django system checks warnings for all known removals from Django v1.0 to today.
Here's an example:
The checks will either be triggered when using the Django development server
python manage.py runserver
or when you call the checks manually
python manage.py check --deploy
It focuses on Django settings but might also add more checks in the future.
Sources
You can read up on Django deprecations in the official docs.
Installation
-
Install the package via pip:
pip install django-removalsor via pipenv:
pipenv install django-removals -
Add module to
INSTALLED_APPSwithin the main djangosettings.py:INSTALLED_APPS = ( # ... "django_removals", )
Since this package adds only Django system checks, which don't run on production, you could add it only when being in (local) debug mode.
if DEBUG_MODE:
INSTALLED_APPS += ("django_removals",)
Releasing a new version
Releases are fully automated. Push a version tag and the pipeline will build, sign with Sigstore, publish to PyPI via Trusted Publishing, and create a GitHub Release — no API tokens needed.
git tag v<version> # e.g. git tag v1.2.3
git push origin v<version>
Tags must start with v. Tags without the prefix won't trigger the pipeline.
First-time setup
Before the pipeline can run for the first time, an admin must:
-
Create GitHub Environment
pypi- Go to Settings → Environments → New environment, name it exactly
pypi - Under Deployment branches and tags, add a tag rule with pattern
v* - Optionally add required reviewers for a manual approval gate
- Go to Settings → Environments → New environment, name it exactly
-
Configure PyPI Trusted Publisher
- Go to PyPI → Project settings → Publishing → Add a new publisher
- Fill in: Owner
ambient-innovation, Repositorydjango-removals, Workflowrelease.yml, Environmentpypi
Publish to ReadTheDocs.io
- Fetch the latest changes in GitHub mirror and push them
- Trigger new build at ReadTheDocs.io (follow instructions in admin panel at RTD) if the GitHub webhook is not yet set up.
Maintenance
Please note that this package supports the ambient-package-update.
So you don't have to worry about the maintenance of this package. This updater is rendering all important
configuration and setup files. It works similar to well-known updaters like pyupgrade or django-upgrade.
To run an update, refer to the documentation page of the "ambient-package-update".
Release files for django-removals 1.5.0
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_removals-1.5.0.tar.gz | 125.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_removals-1.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 132.9 kB
Release files / django_removals-1.5.0.tar.gz
| Download URL | django_removals-1.5.0.tar.gz |
|---|---|
| Size | 125.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
091cfbf63fc02d4a3c287f6c136f692f05848186d75ac47219de31b78bde4f1f
|
|
BLAKE2b-256 checksum How to use checksums |
7a31951f7129f8ee65af450a12997ff99de56a33c5c8992b97c28d8968a764e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 27, 2026.
Transparency logRelease files / django_removals-1.5.0-py3-none-any.whl
| Download URL | django_removals-1.5.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4b725b4fde07356afd9c8ed302e1b7a3172bb674d897c4b4a4f98ed811305046
|
|
BLAKE2b-256 checksum How to use checksums |
128145ec97424c4941aec2b02d7b12f6108632bf04c244afd1c1a8fffdd5a9dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 27, 2026.
Transparency log