News for hackers. Stuff that matters.
Re:Django 3 by gonational on Monday December 02, 2019 @08:56AM (#21682283)
If you can convince your company to keep Django up-to-date with every release, I have found this to be easy and pain-free (Django has been pretty API stable since ~1.8), compared with waiting for each LTS and then being forced to jump ahead three versions each time.

You also gain access to new features as they come out, this way.

Re:Django 3 by primozk on Monday December 02, 2019 @10:04AM (#21682923)
But you have to be careful that all dependencies are up-to-date as well.
Re:Django 3 by vdfs on Monday December 02, 2019 @10:18AM (#21683072)
No to mention each new release have many incompatibility that you need to read the release note to find out
Re:Django 3 by BozeWolf on Monday December 02, 2019 @11:54AM (#21684177)
Django is very good at being backwards compatible. Deprecated functions emit warnings for a few releases before being removed. They are also documented.

Do you have some examples? Are you sure you are not confused with dependencies?

The release notes mention less than ten deprecations related to django. Other stuff which is not supported anymore is mostly non supported database versions.

https://docs.djangoproject.com/en/3.0/releases/3.0/#backward...

Re:Django 3 by marcosdumay on Monday December 02, 2019 @12:18PM (#21684424)
The Django incompatibilities is a small problem. If you do sign-up for the theory that it's better to use its ecosystem, the changes on the related projects are much larger.