Changelog for python311-django-taggit-5.0.1-2.1.noarch.rpm :

* Sat Jan 18 2025 ecsos - Add %{?sle15_python_module_pythons}- Add missing build require python-pytz.
* Sat Nov 25 2023 Dirk Müller - update to 5.0.1:
* Fix the package metadata to properly reflect the right Django and Python version requirements
*
*
*Backwards icompatible:
*
* Rename the (``content_type``, ``object_id``) index on ``TaggedItem``.
* Remove support for Django 3.2.
* Remove usage of deprecated APIs for Django 4.2
* Remove support for Python 3.7 (no code changes involved)
* Fix ``tag_kwargs`` and ``TAGGIT_CASE_INSENSITIVE=True`` discrepency.
* Fri May 05 2023 Markéta Machová - update to 4.0.0
* Remove Python 3.6 support (no code changes occurred, but we no longer test this release).
* Remove Django 4.0 support (no code changes occurred, but we no longer test this release).
* Add Django 4.2 support.
* Wed Jan 04 2023 Dirk Müller - update to 3.1.0:
* Add Python 3.11 support
* Add Django 4.1 support
* Fixed an issue where object caches would not be properly cleared after updating tags, leading to stale reads in cases where ``prefetch_related`` is used.
* Change ``TagListSerializerField`` to be a subclass of ``ListField``. This should improve support for API document generation. This change should not affect API behavior, but might affect metaprogramming code, so please procede carefully during this update.
* Sat Oct 15 2022 John Vandenberg - Activate test suite- Update to v3.0.0
* Backwards incompatible: Tag slugification used to silently strip non-ASCII characters from the tag name to make the slug. This leads to a lot of confusion for anyone using languages with non-latin alphabets, as well as weird performance issues.
* Tag slugification will now, by default, maintain unicode characters as-is during slugification. This will lead to less surprises, but might cause issues for you if you are expecting all of your tag slugs to fit within a regex like [a-zA-Z0-9] (for example in URL routing configurations).
* Generally speaking, this should not require action on your part as a library user, as existing tag slugs are persisted in the database, and only new tags will receive the enhanced unicode-compatible slug.
* If you wish to maintain the old stripping behavior, set the setting TAGGIT_STRIP_UNICODE_WHEN_SLUGIFYING to True.
* As a reminder, custom tag models can easily customize slugification behavior by overriding the slugify method to your business needs.
* Drop Django 2.2 support.
* Wed Apr 13 2022 Misha Komarovskiy - Update to 2.1.0
* Add Python 3.10 support.
* Add Django 4.0 support.
* Drop Django 3.1 support.
* Tue Dec 07 2021 Misha Komarovskiy - Update to 2.0.0
* Backwards incompatible: TaggableManager.set now takes a list of tags (instead of varargs) so that its API matches Django\'s RelatedManager.set
* Fix issue where TagField would incorrectly report that a field has changed on empty values.
* Update Russian translation.
* Add Persian translation
* Fix issue for many languages where content types were not being properly translated.
* Provide translators additional context regarding strings in TagBase model.
* Wed Jul 07 2021 Daniel Molkentin - Update to 1.5.1
* Fix compiled Ukranian translation (which would cause a failure on load for this locale).
* Update compiled Danish translation.- Update to 1.5.0
* Vendor in the django-taggit-serializer project (under taggit.serializers).
* Add Arabic translation.
* Add Ukranian translation.
* Mon May 10 2021 Daniel Molkentin - Update to version 1.4.0
* Bump the taggit version number to 1.4.0
* Mon Aug 24 2020 Daniel Molkentin - Update to version 1.3.0
* Model and field verbose_name and verbose_name_plural attributes are now lowercase. This simplifies using the name in the middle of a sentence. When used as a header, title, or at the beginning of a sentence, a text transformed can be used to adjust the case.
* Fix prefetch_related when using UUIDTaggedItem.
* Allow for passing in extra constructor parameters when using TaggableManager.add. This is especially useful when using custom tag models.