I guess I don't really see how we'd be helping users in any meaningful way by supporting python 3.4 with Django 2.0. Django 2.0's defining change is dropping Python 2. We have no idea what else will land in 2.0.
If we're trying to consider Enterprise users on "older" Distros: - 1.11 will be LTS and will be supported for **longer** than Django 2.0 will be. - 1.11 supports 2.7 through to 3.6. - The next LTS, which is likely the next version of Django for these Users, will support 3.6+ If we're wanting users to upgrade their code bases to run on Python 3, then they certainly won't be doing it on Django 2.0. If they plan to move to Python 3 at all, it'll be on 1.11 or 2.2. And if they want to be running on the latest and greatest Django, then why shouldn't that extend to adding an RPM repo or RedHat-SCL and installing the latest Python? I admit to a lack of knowledge on how to install new versions of Python on Ubuntu-likes. But https://ius.io/ is a great Redhat/Centos repo for installing newer Python versions. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a42c0ae6-7291-4643-b558-1b29bcb65081%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
