Django 1.7 vs Django1.6 vs Django 1.5 [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 8 years ago.

Improve this question

I have been developing using Django 1.5 a lot. Is it worth the time to shift from Django 1.5 to Django 1.6 or Django 1.7? I know, In 1.7, migration is into the core of Django. How different is it from south?

Answer 1

Django 1.6 is a relatively incremental update compared to Django 1.7.

Django 1.6 adds a few comfort features (i.e., simplified project templates and admin enabling by default) for new projects, and some minor overhauls in algorithms (i.e., model save). There are also a myriad of other features that make development relatively easier when compared to 1.5.

Django 1.7, as you've noted, includes the migration features. In addition, it forces Python 2.7 (which may or may not be an issue for you). The migration is based off of South, so it's similar to use. In addition to various improvements, the plugin focused on being database agnostic, improved autodetection and improved the migration file format.

With both of these updates, your workflow shouldn't change significantly.