This series of Django releases was supported from 2017-04-04 to 2020-04-01.

Highlights

Django 1.11 was a long-term support release. Extended support ended on 2020-04-01.

With most people having either moved to Python 3 or working on moving, this is the last version of Django that will support Python 2.

Until this release, there weren’t a lot of options for adding indexes to model fields. You basically had single column indexes, single column unique indexes, and multi-column indexes. In Django 1.11, there are now class-based model indexes. These are a bit more flexible and make way for some neat PostgreSQL specific index options.

The Django admin date_hierarchy feature can now reference fields across relationships. It’s a smaller feature, but one we’ve all run into at least once in the past.

This release also deprecates several features you may be using. If you’re hopping from LTS to LTS, you’ll want to make plans for changing how you are using these features before it’s time to upgrade.

Upgrade Gotchas

• pytz is now a required dependency, which isn’t all that surprising but is definitely worth noting.
• There are also several GeoDjango (aka django.contrib.gis) changes that might get in your way when upgrading from v1.10.
• django.forms.Widget.render added the renderer keyword.