django-taggit-anywhere
Even more simpler approach to tagging with django-taggit. Additionally this project provides easy-to-use integration with django-taggit-helpers and django-taggit-labels
Installation
First install the module, preferably in a virtual environment. It can be installed from PyPI:
pip install django-taggit-anywhereRequirements
You must have django-taggit installed and configured, see the django-taggit documentation for details and setup instructions.
Setup
Make sure the project is configured for django-taggit.
You’ll need to add taggit_anywhere as a LAST item to INSTALLED_APPS in your project’s settings.py file:
INSTALLED_APPS += [
# optional integration with django-taggit-helpers
'taggit_helpers', # pip install django-taggit-helpers
# optional integration with django-taggit-labels
'taggit_labels', # pip install django-taggit-labels
'taggit_anywhere', # must be last in a list
]There is only one mandatory configuration option you need to set in your settings.py:
TAGGIT_FOR_MODELS = [
'<app_name>.<model_name>',
]Please see example application. This application is used to manually test the functionalities of this package. This also serves as good example…
You need Django 1.8 or above to run that. It might run on older versions but that is not tested.
Contributing
If you like this module, forked it, or would like to improve it, please let us know! Pull requests are welcome too. :-)
License
django-taggit-anywhere is released under the MIT license.
Changes
2.1.0 (2026-10-10)
Dropped Python < 3.11 support; 3.11 is now the minimum requirement.
Added Python 3.15 support.
2.0.0 (2026-08-14)
Dropped Python < 3.10 support; now tested on Python 3.10-3.14.
Dropped Django < 5.2 support; now tested on Django 5.2, 6.0 and 6.1.
Fixed AppConfig.ready()’s “already tagged” guard, which was unreachable dead code and would raise ValueError if ready() ever ran twice.
1.0.0 (2021-11-29)
Added Django 3+ support.
Dropped Python 2.7 support.
Dropped Django 1.10 / 1.11 support.
1 maintainer
Metadata
1 maintainer
Release files for django-taggit-anywhere 2.1.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_taggit_anywhere-2.1.0.tar.gz | 6.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_taggit_anywhere-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.6 kB
Release files / django_taggit_anywhere-2.1.0.tar.gz
| Download URL | django_taggit_anywhere-2.1.0.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3953b7a79b09ca4903b5bbad1c22ec6ad0e0f91dc2cad3bbbc2f62d154cb124f
|
|
BLAKE2b-256 checksum How to use checksums |
12be443e5f5e8c6bd0f2265c93697739e9f01c6753bcc3a261e73367193c10d9
|
| 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 Oct 10, 2026.
Transparency logRelease files / django_taggit_anywhere-2.1.0-py3-none-any.whl
| Download URL | django_taggit_anywhere-2.1.0-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fce207e0e911621f337ab3ed7379ab41dc5c457cc240fe3a2edf25365d7703b9
|
|
BLAKE2b-256 checksum How to use checksums |
25feb21cda5c3dae896d9eff1f5e3b22b20a54dcdd7c5ad2b11e3e1b132104b7
|
| 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 Oct 10, 2026.
Transparency log
