Closed barseghyanartur closed 3 years ago
Not specifically, actually, starting from 1.11 code migrations in Django are much simpler. Minimally, test suite shall be changed to include 2.2 and 3.0 to proclaim that they are supported. And pending deprecations shall be addressed (often, conditionally, using django-nine
).
Done in master.
I have this working with Django 3, is there a specific issue with 2.2 ?