Django-Flags
Feature flags allow you to toggle functionality in both Django code and the Django templates based on configurable conditions. Flags can be useful for staging feature deployments, for A/B testing, or for any time you need an on/off switch for blocks of code. The toggle can be by date, user, URL value, or a number of other conditions, editable in the admin or in definable in settings.
- Dependencies
- Installation
- Documentation
- Getting help
- Getting involved
- Licensing
- Credits and references
Dependencies
- Python 3.10+
- Django 4.2+
Installation
- Install Django-Flags:
pip install django-flags
- Add
flagsas an installed app in your Djangosettings.py:
INSTALLED_APPS = (
...
'flags',
...
)
Documentation
https://cfpb.github.io/django-flags is the full documentation for Django-Flags, and includes how to get started, general usage, and an API reference.
Getting help
Please add issues to the issue tracker.
Getting involved
General instructions on how to contribute can be found in CONTRIBUTING.
Licensing
Credits and references
Django-Flags was forked from Wagtail-Flags, which was itself forked from cfgov-refresh.
Metadata
Release files for django-flags 5.2.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_flags-5.2.0.tar.gz | 246.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_flags-5.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 289.6 kB
Release files / django_flags-5.2.0.tar.gz
| Download URL | django_flags-5.2.0.tar.gz |
|---|---|
| Size | 246.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3aee5e0d11e24e35f5ae4a423d52cad721f639181c1b1251e0148d8530a3f81
|
|
BLAKE2b-256 checksum How to use checksums |
72e7da3a2e006a670c4c275fa0abd15ab4715576bb933d9e97ae4f9477cd8a88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 10, 2026.
Transparency logRelease files / django_flags-5.2.0-py3-none-any.whl
| Download URL | django_flags-5.2.0-py3-none-any.whl |
|---|---|
| Size | 42.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa22543410f68a4082c576f3be469ea67a51c933f8a43eb8b10f6236f158e17e
|
|
BLAKE2b-256 checksum How to use checksums |
15e694dcb6cea2ede9adcd406f48ff04ce80bdb5a919306f1aded8d84e27f807
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 10, 2026.
Transparency log