Skip to main content
https://badge.fury.io/py/django-taggit-anywhere.svg https://img.shields.io/pypi/pyversions/django-taggit-anywhere.svg https://img.shields.io/pypi/djversions/django-taggit-anywhere.svg https://github.com/bashu/django-taggit-anywhere/actions/workflows/test.yml/badge.svg

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-anywhere

Requirements

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.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.

Metadata

Release files for django-taggit-anywhere 2.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-taggit-anywhere 2.0.0
File Size Uploaded
django_taggit_anywhere-2.0.0.tar.gz 9.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for django-taggit-anywhere 2.0.0
File Interpreter ABI Platform
django_taggit_anywhere-2.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 19.2 kB

Release files / django_taggit_anywhere-2.0.0.tar.gz

Download URL django_taggit_anywhere-2.0.0.tar.gz
Size 9.2 kB
Tags Source
SHA-256 checksum
How to use checksums
6dc37e57ec2252bf8b5ac82736a938ec9b55ce8de362ee120181c36f7eeea3f0
BLAKE2b-256 checksum
How to use checksums
af4f43841ec1d5cbd6cb31932acf038825593940a120974bbfb92f3351d84ecb
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 14, 2026.

Transparency log

Release files / django_taggit_anywhere-2.0.0-py3-none-any.whl

Download URL django_taggit_anywhere-2.0.0-py3-none-any.whl
Size 10.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
dd7298179aebb78668c0d054793ddd550f1ed9ada4ed84b8e075adcdfb27a713
BLAKE2b-256 checksum
How to use checksums
44bbae651d4508ee94ade29ee86a772db8aba49f040625ef101603825255b2df
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 14, 2026.

Transparency log

Release history Release notifications | RSS feed

2.1.0

2 release files

This release

2.0.0 This release

2 release files

1.0.0

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page