I often hear Ubuntu thrown around during these discussions, and it is my distro of choice for personal projects. But like many of us, I work at a RedHat / CentOS shop, and trying to maintain a current Python version is a much more difficult proposition. Unfortunately, IUS Community has stopped providing yum-installable versions of Python in an attempt to get EPEL to be more up to date, but that hasn't happened. To get a version of Python greater than 3.6 on RedHat / CentOS, AFAIK, you currently must build from source with altinstall.
I agree with Andrew's statement that we should consider each version. I can see dropping Python 3.5 support - it would allow us to use a feature like f-strings, which improves readability and speed throughout the codebase, and is ubiquitous in Python. But what does dropping Python 3.6 support really achieve? Do we need data classes? I realize there is a need to move forward, especially for wonderful things like better async support. I just ask that we also consider those of us using Django in corporate or academic settings where the pace of upgrading Python is a bit more glacial. On Thursday, November 19, 2020 at 11:51:29 AM UTC-5 Andrew Godwin wrote: > I agree we should not be quite so beholden to our existing Python version > policy - that was mostly to get us out of the early 3.x era. Now things are > more stable, I'd support a policy that is much more like "any stable > version of Python currently out there and supported". > > Andrew > -- 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/83fc7a73-aa7d-4390-805f-c50c496175f8n%40googlegroups.com.
