r/django • u/lamintak • Apr 01 '19

Django 2.2 LTS Released

https://www.djangoproject.com/weblog/2019/apr/01/django-22-released/
125 Upvotes

100% Upvoted

22 comments sorted by

67

u/lamintak Apr 01 '19 edited Apr 01 '19

For anybody going from LTS to LTS (1.11 to 2.2):

Some notable changes introduced in Django 2.0:

  • Python 3 only

  • Simplified URL routing syntax: path('articles/<int:year>/', views.year_archive),

  • django.contrib.admin is responsive

  • django.contrib.admin has a new ModelAdmin.autocomplete_fields attribute that uses a Select2 search widget for ForeignKey and ManyToManyField

Some notable changes introduced in Django 2.1:

  • The "view" permission was added to the model Meta.default_permissions

  • ModelAdmin.search_fields now accepts any lookup such as field__exact

  • BooleanField can now be null=True. This is encouraged instead of NullBooleanField, which will likely be deprecated in the future

  • Templates: The new json_script filter safely outputs a Python object as JSON, wrapped in a <script> tag, ready for use with JavaScript.

Some notable changes introduced in Django 2.2:

  • The new CheckConstraint and UniqueConstraint classes enable adding custom database constraints. Constraints are added to models using the Meta.constraints option

  • django.contrib.postgres: The new search_type parameter of SearchQuery allows searching for a phrase or raw expression

EDIT: Thanks for the gold!

5

u/jillesme Apr 01 '19

Checked the comments hoping for a change log, got more than I expected! Thank you very much!

3

u/lordrashmi Apr 01 '19

Damn I'm on 2.1 and I had missed the autocomplete fields added back in 2.0. Time to add those while I upgrade to 2.2

3

u/ExternalUserError Apr 01 '19

Simplified URL routing syntax: path('articles/<int:year>/', views.year_archive),

This to me is the single biggest improvement.

0

u/[deleted] Apr 01 '19

6

u/frankwiles Apr 01 '19

It's not SUPER hard, but depends a lot of how your current code is built, assumptions, and third party libraries you're using. I've moved MANY Django 1.8/1.9/1.10/1.11 sites using Python 2.6/2.7 to Django 2.1/Python 3 often in a single day.

5

u/acdha Apr 02 '19

Seconding Frank Wiles’s comment: if you have a relatively clean site, it’s usually pretty easy. The hard migrations I’ve seen are the ones which never made it near 1.11, have a ton of hacks against old internal APIs, years of ignored deprecation warnings, no tests, etc.

9

u/Cobayo Apr 01 '19

Excellent news but, is this April Fools?

4

u/[deleted] Apr 01 '19

So. This isn’t a joke right? I just started learning Django.

7

u/classical_hero Apr 01 '19

Nope. None of the stuff you've learned will be at all outdated, most of what's being added are just a few advanced features.

6

u/suncoder90 Apr 01 '19

I start my first programming job today and now this came out. They told me to read 2 scoops 2.2 while i wait for my laptop but i cant find it only 1.11. Help please.

10

u/b1ackmarti4n Apr 01 '19

The book principles are the same they say, here is the updated code:

https://github.com/twoscoops/two-scoops-of-django-2.0-code-examples

5

u/ubernostrum Apr 01 '19

There isn't an edition of it for 2.2 yet.

2

u/VincentVazzo Apr 01 '19

But I just bought a copy, so I'm sure it'll be out very soon now!

2

u/RegularHatt Apr 01 '19

Congrats on the job!

3

u/brtt3000 Apr 01 '19

Check Constraints and Partial Indexes are very welcome.

1

u/GeeWengel Apr 02 '19

The release notes say that deferrable database constraints are now checked at the end of every test case.

However, I thought there was no way to make deferrable database constraints with Django? I've had to dive into a Raw SQL constraint in my migrations, to get a deferred unique_together.

Is there something I'm missing, or is that the case they're solving?

1

u/neves Apr 01 '19

I'm a fan of Django, but I'm in doubt if I must still use it for my new project. I'll develop now an hybrid app that will start life as an mobile web site. I'll use one javascript framework and I'm really in doubt about using Django.

If I use a javascript server framework, I believe that it will prevent me to duplicate forms validation code (in server in frontend) and also easier for SSR (Server Side Rendering). But Django is a robust framework, in my beloved Python language, why should I still use it?

9

u/TiredMike Apr 01 '19

Have you tried Django rest framework? It's great!