Closed wizpig64 closed 2 years ago
what about dropping 3.0
Sure thing. There probably won't be any code changes though until 2.2 is dropped.
yeah
I force pushed new changes dropping django 3.1, as well as the contrib._pipeline
package, which was holding us back. If this gets merged today I'm going to release it as v2.10.0
b1, with more old-code cleanup.django.conf.urls.url
in test app (gone in Django 4.0).DEFAULT_AUTO_FIELD
to avoid warnings in test app.Switch todjango-pipeline>=1.6.0
-stylePIPELINE
settings.django_jinja.contrib._pipeline
package, which was deprecated in 2015.I'll be leaving this as a draft until django-pipeline is updated to support Django 4.0: https://github.com/jazzband/django-pipeline/pull/760