Django 1.11 beta 1 is an open door for you to experiment with the mixture of new components in Django 1.11.
Just bugs in new components and relapses from prior variants of Django will be settled amongst now and 1.11 last (additionally, interpretations will be redesigned taking after the “string solidify” when the discharge applicant is issued)
Likewise with all alpha and beta bundles, this is not for creation utilize. Be that as it may, on the off chance that you’d jump at the chance to take a portion of the new elements for a turn, or to help discover and settle bugs (which ought to be accounted for to the issue tracker), you can snatch a duplicate of the beta bundle from our downloads page or on PyPI.
The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252.
Compatibility with Python
Django 1.11 requires Python 2.7, 3.4, 3.5, or 3.6. Django 1.11 is the primary discharge to bolster Python 3.6. It’s exceedingly suggest and just formally bolster the most recent arrival of every arrangement.
The Django 1.11.x arrangement is the last to bolster Python 2. The following real discharge, Django 2.0, will just bolster Python 3.5+.
Deprecating warnings are no longer loud by default
Not at all like more seasoned renditions of Django, Django’s own particular censure notices are no longer shown as a matter of course. This is reliable with Python’s default conduct.
This change permits outsider applications to bolster both Django 1.11 LTS and Django 1.8 LTS without adding code to maintain a strategic distance from belittling notices.
Taking after the arrival of Django 2.0, we recommend that outsider application creators drop bolster for all renditions of Django before 1.11. Around then, you ought to be capable run your bundle’s tests utilizing python – Wd so that censure notices do show up. In the wake of making the belittling cautioning fixes, your application ought to be perfect with Django 2.0.
What’s new in Django 1.11
Class-based model indexes
django.db.models.indexes module contains classes which ease creating database indexes. Indexes are added to models using the
Index class creates a b-tree index, as if you used
db_index on the model field or
index_together on the model
Meta class. It can be subclassed to support different index types, such as
GinIndex. It also allows defining the order (ASC/DESC) for the columns of the index.
Template-based widget rendering
To ease customizing widgets, form widget rendering is now done using the template system rather than in Python. See The form rendering API.You may need to adjust any custom widgets that you’ve written for a few backwards incompatible changes.
The new Subquery and Exists database expressions allow creating explicit subqueries. Subqueries may refer to fields from the outer queryset using the OuterRef class.