← Back to Topics

Django Version Support

Comments discuss Django's release cycles, LTS support, upgrade challenges between versions like 1.4 to 1.8, and the slow transition to full Python 3 compatibility.

➡️ Stable 0.6x Web Development
1,268
Comments
18
Years Active
5
Top Authors
#9255
Topic ID

Activity Over Time

2008
33
2009
29
2010
80
2011
85
2012
142
2013
184
2014
91
2015
59
2016
58
2017
143
2018
39
2019
72
2020
34
2021
54
2022
25
2023
56
2024
34
2025
50

Top Contributors

ubernostrum (27) jacobian (24) collinmanderson (22) jsmeaton (19) huxley (11)

Keywords

RC e.g IMHO djangoproject.com EOL COBOL LTS github.com DjangoCon i.e django python release lts support eol version 2020 major version fixes

Sample Comments

mememememememe • Nov 25, 2012 • View on HN

Django 1.4.2 is still alive! 1.5 support for Python 3 is still considered "experimental". It wouldn't get mature until 1.7, or even 1.7 IMHO. Python community is now stuck at 2.6.5/6, 2.7.3 and 3.x, which does screws people over. Lots of changes in 3.3 now. I am not even sure if 2.7.x is catching up with the 3.3 branch. I doubt.

aerolite • Jun 28, 2013 • View on HN

Christ, Django is changing too fast. I recently upgraded from 1.2 to 1.3 and it's still way obsolete.

minimaxir • Dec 2, 2015 • View on HN

Not for a couple years: https://www.djangoproject.com/weblog/2015/jun/25/roadmap/

huxley • Oct 20, 2012 • View on HN

Python 3 support was --last I heard-- still considered experimental/alpha by the core team in the upcoming Django 1.5 release, so I would assume if it treats it at all, it will be mostly to encourage forward-compatible programming practices.

po • Jan 19, 2017 • View on HN

That's pretty much true of any django release... you can stay on it if you so choose to. It will get security updates/bug fixes for a bit and then they will stop coming. You're free to stay where you are if you want.It turns out that most developers have a desire to move to the next version if it's not too hard. There's still COBOL programmers out there too and that's perfectly fine.Django has made the process as smooth as it can be. You can upgrade to python3

sirodoht • Dec 2, 2017 • View on HN

Respect to the Django team that even after 12 years they have only one major version shift (which seems to only because of dropping support for Python 2) and the backwards incompatible changes are minimal.

ubernostrum • Mar 13, 2012 • View on HN

Wait till this fall when we release Django 1.5 :)

dnsauve • Nov 28, 2009 • View on HN

Anyone else confused by this opening statement: "Python 3 has been out for about a year at this point, and so far Django hasn't really started to move towards it (at least at a first glance). However, Django has already begun the long process towards moving to Python 3[...]"?

bildung • Dec 2, 2019 • View on HN

I feel your pain. If maintainability is your concern, I would advice to skip this release as it won't have long term support. The current LTS release is still 2.2 and will only be replaced with 3.2 sometime in 2021.You probably already know, but the long term release timeline is shown at https://www.djangoproject.com/download/Sticking with LTS releases really helps. You'll

mtbcoder • Jun 9, 2015 • View on HN

Regarding Python, Django does LTS releases.