I think that the main reason for supporting Python 3.7 in Django 1.11 was to help make things easier for those migrating from Python 2 to 3.
Python 3.8 was only released ~3 months before the Python 2 EOL, so most people in the last year and up to the end of this year will likely migrate to Python 3.7. I also feel the policy was a little aggressive given that the total change to support Python 3.7 was https://github.com/django/django/compare/216398d1...c11a7b4 So +1 to Python 3.8 for Django 2.2, with an option on Python 3.9 if trivial. On Wednesday, 30 October 2019 14:44:20 UTC, Carlton Gibson wrote: > > Hi all. > > In November last year we added official Python 3.7 support to Django 1.11. > > https://groups.google.com/d/topic/django-developers/H7fP5w0YU2I/discussion > > This was 18 months after release, and well into the extended support > period. > > There had been a long-line of requests to add that support. It seems that > lots of users want both the latest > Python and the Django LTS. > > > Django 2.2 officially only supports Python 3.8. > > Python 3.8 is already available. > > Python 3.9 will be available Oct 2020, which is a ≈18months before 2.2. is > EOL, and is roughly equivalent to when we added support for Python 3.7 to > Django 1.11. > > > I predict a similarly strong demand to support the newer Python versions > in Django 2.2. > > I'm happy to take whatever line we deem appropriate here, but I'd like to > avoid, for example, saying "No, it's not supported" for many months, before > then changing our minds. > > So what shall we do? > > Django 2.2 is still in mainstream support and I think it should > automatically get Python 3.8 support. > I think version of Django should support the new Python versions whilst in > mainstream support, but I think this applies doubly to the LTS, even though > the LTS isn't my thing, simply because of the demand for it. > > Data point: I didn't test the full matrix but, tests are already passing > here. > > For Python 3.9 I think we should probably declare now that we will review > whether we will support it for 2.2 LTS when it's released. > (i.e. if it's a small back port like the one required for 3.7/1.11 then > yes, otherwise no.) > > > What do we think? > > Thanks > Kind Regards, > > Carlton > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/613aee69-1d8b-445c-a64b-0917eed976a7%40googlegroups.com.
