Django Evolution 2.4 adds a new feature to help when moving away from legacy Django model field types.

Field Type Module Updates

We've added a new setting to help when moving from a field type in an old module path to a new one, whether that field type has simply been moved or is completely gone and replaced with a compatible one.

This is done by setting DJANGO_EVOLUTION['RENAMED_FIELD_TYPES'] in settings.py to a a dictionary mapping old field module paths to the new ones. Any time the old path is referenced in any evolution or stored signature data, the new path will be used instead.

For example:

DJANGO_EVOLUTION = {
    'RENAMED_FIELD_TYPES': {
        'myproject.MyField': 'myproject.fields.MyField',
    },
}

Installation

$ pip install django-evolution==2.4

Learn More

• Django Evolution 2.4 release notes
• Documentation
• PyPI

Django Evolution 2.3 adds compatibility with Python 3.12 and all versions of Django between 1.6 and 4.2, along with new features and enhanced options for diagnosing bad upgrades.

Highlights

• Added support for Python 3.12.
• Added support for Django 4.2.
• Added the ability to evolve table comments on Django 4.2.
• Added advanced management commands for working with and debugging project signatures and marking evolutions as applied.
• Added debug logging for the evolution process.

Installation

$ pip install django-evolution==2.3

Learn More

• Django Evolution 2.3 release notes
• Documentation
• PyPI