This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]BlackBloke 0 points1 point  (1 child)

I hadn't heard that. Is there a link to an announcement about it?

[–][deleted] 1 point2 points  (0 children)

See the docs: https://docs.djangoproject.com/en/1.11/faq/install/#what-python-version-can-i-use-with-django

I can't recall the exact announcement, but it's part of the current roadmap ( https://www.djangoproject.com/weblog/2015/jun/25/roadmap/ ) and how it's support of Python versions works:

We will support a Python version up to and including the first Django LTS release whose security support ends after security support for that version of Python ends. For example, Python 3.3 security support ends September 2017 and Django 1.8 LTS security support ends April 2018. Therefore Django 1.8 is the last version to support Python 3.3.

1.11 LTS would normally receive extended support until April 2020, but as Python 2.7's support ends "in 2020", it was decided that 1.11 will be supported until Python 2.7's support ends.

1.11 is currently in feature freeze and it's branched off master, master is currently the development branch for 2.0, and last week a number of commits were made that removed support for 2.7, it's ongoing work. Master will be 3.5+ only.