Looking at this again, I'm not sure it would be six versions. Carlton's suggested policy has the effect of dropping a lot of Python versions right before the LTS since it's supported for 3 years. For example, in Django 5.2 LTS, I think it's incorrect that Python 3.10 and 3.11 would be supported since their support expires in Oct 2026 & 7, before Django 3.2's expiration in April 2028)? The current policy means we have Django LTS's supporting some Python's well after they expire. I never liked that aspect of it. Anyway, the decision won't affect my life. On Tuesday, January 26, 2021 at 5:32:50 AM UTC-5 Mariusz Felisiak wrote:
> Hi y'all, > > I think we should keep the current policy. There is never a good time > to drop support for anything and extending support especially for Python > 3.7 will end with more exceptions in the future. Current policy is really > patronizing and with the new Python release schedule we can reach 6 > supported versions of Python for every LTS. I would make it even more > aggressive :) It's not only about the maintenance burden but also about new > features and syntax, we have tickets waiting 2-3 years until Python X > becomes the minimal Python supported by Django. My 2 cents 🤷 > > Best, > Mariusz > >> -- 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 django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4dd42d46-ffe7-432f-8572-5a261c4fd0fcn%40googlegroups.com.
