I'm in the camp of having a flexible policy that allows us to have discussions that examine the current state of the Django and Python ecosystems. This allows us to make informed decisions.
As several folks have mentioned before, 3.6 was a more momentous release than most versions of Python. Since moving to it, features that I didn't think I'd like initially have grown into ones I couldn't imagine working without, such as f-strings. Easier to read, less cognitive load of "fill in the blank" replacement, more beautiful code, straightforward to explain newcomers, and faster?! That's just one example of a huge win that might lower the bar to entry of contribution to Django. More efficient memory use in dicts and type annotations are other big wins. I typically might lean to the side of supporting versions for longer, but in this case, I'm firmly in the 3.6 camp because of the nature of the release. I also thought I'd mention that within my organization, the version of Python that Django supports is a driver that I appreciate. While some groups keep up with the latest Python versions, other groups aren't as good, only upgrading when necessary. I won't get into the politics of the developers who want newer versions versus sysadmins who don't want to change, but I've appreciated Django helping move things forward. -- 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 post to this group, send email to email@example.com. 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/d108f73f-72cc-4180-a26b-95920413adcf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.