Releases: niwinz/django-jinja
Releases · niwinz/django-jinja
Version 2.11.0
- Drop Django 2.2 support, now require >=3.2.
- Drop Python 3.6 and 3.7 support, now require >=3.8.
- Add Django 4.1 and 4.2 support.
- Add Python 3.11 support.
- Provide a better default template engine NAME than 'backend' (#303):
Previously, when configuring TEMPLATES
in Django's settings, NAME
had to be set to avoid the template engine's name becoming "backend"
:
TEMPLATES = [
{
"NAME": "jinja2",
"BACKEND": "django_jinja.backend.Jinja2",
If your code matches that pattern, it can now be simplified to:
TEMPLATES = [
{
"BACKEND": "django_jinja.jinja2.Jinja2",
There are no plans to remove support for the old backend
import path, for consideration of existing projects. Also, be careful if you've set NAME
to "jinja"
(not "jinja2"
)!
Version 2.10.2
- Fix compatibility with Jinja2 3.1 in tests (#296).
Version 2.10.1
- Update links in documentation to point to new home of Jinja2 docs (#295).
Version 2.10.0
- Fix usage of
unittest
to be ready for Python 3.11 (#288). - Fix
default_app_config
deprecation warning for Django 3.2 (#289). - Replace Travis with GitHub Actions, dropping
ppc64le
arch tests (#290).- Added Python 3.10 to tests (Django supports it if >=3.2.9).
- Run pyupgrade, remove compatibility code (#291).
- Add support for Django 4.0, with more old-code cleanup (#292).
- Remove use of
django.conf.urls.url
in test app (gone in Django 4.0). - Set
DEFAULT_AUTO_FIELD
to avoid warnings in test app. - Remove
django_jinja.contrib._pipeline
package, which was deprecated in 2015. - Drop formal Django 3.0 and 3.1 support.
- Projects using these versions should still function until support for 2.2 is dropped.
- Remove use of
- Django 2.2 and Python 3.6 will likely be dropped in the next non-patch release.
Version 2.9.1
- Complete config example in the docs now reflects actual project defaults (#286).
get_template
no longer callstemplate_name.endswith
twice under the default setup.- Rewrite usage and template matching config sections in the docs, to fully explain behavior.
Version 2.9.0
- Jinja2 policies now settable via
TEMPLATES[n]['OPTIONS']['policies']
(#285). makemessages
now respects theext.i18n.trimmed
policy,
will automatically trim jinja{% trans %}
blocks when generating.po
files.
Version 2.8.0
- Upgrade to jinja2 3.0, dropping support for 2.11 and below (#279).
- Dropped Python 3.5 support.
Version 2.7.1
- Fixed
makemessages
command, which in 2.7.0 could not detect{% trans %}
tags in Django templates (#272). - Fixed
{% cache %}
tag to allow a timeout ofNone
(to cache forever), which Django's tag added in 2.0 (#274). - Fixed README not displaying in project description at PyPI (#276).
- Added Django 3.2 support.