Add support for Django 3.0.
Review Request #11095 — Created July 23, 2020 and submitted
This enables support for Django 3.0. There were only two major
difference between Django 2.2 and 3.0 that impacts Django Evolution:
- The removal of
- A change to the internal structure of applied migration lists in the
migration machinery, which we override in order to inject our own
Those were both primarily taken care of by the past two commits. This
commit builds upon the new
MigrationListclass to transform to the
proper internal structure, depending on the version of Django.
There's also a small change to the ordering of SQL statements generated
when constructing a
ManyToManyField's intermediary table on MySQL and
Postgres, which just requires some shuffling in the SQL test mapping
Other than that, there isn't really anything left that's specific to
The documentation and package dependencies have been updated to include
Django 3.0 support.
Unit tests pass for all supported versions of Python and Django.
Updated the MySQL/Postgres SQL test files for SQL ordering changes for M2M intermediary tables.
Revision 2 (+540 -22)
Checks run (2 succeeded)