I understand my obsession for stable software puts me in a small-minority
group and I would not like to be an obstacle for all other Django users and
Let's stick to the current policy. I'll try to remember that and prevent
commenting on the next " Drop python support..." ticket :-)
I like stability too, but I think Django's current policy is useful for
driving the ecosystem forwards. Users sticking on old/stable versions of
Python can stick on old/stable versions of Django :)
On Tue, 22 Jan 2019 at 10:07, Claude Paroz wrote:
> I understand my obsession for stable software
Chiming in. As a long-time django user (nearly a decade), websockets is an
area that the project on the whole is very, very, far behind the leading
edge of the web industry. It's great, often desirable, to not be *on* the
leading edge, but in my opinion, the project is too far behind it.
We can look at the larger distros (Debian, Ubuntu, RHEL). For RHEL, their
derivatives include CentOS , Scientic Linux, Amazon Linux, Oracle Linux.
RHEL 7 has no (main) Python 3 support. It's only introduced in RHEL 8
(which is currently in beta).
That gives us for Debian Stretch (stable) and
I would ask: what are the pros and cons of dropping support for python 3.5?
I think allowing users to easily use and install django based applications
is more important than strictly follow a python version support policy.
I think that if we drop support for python 3.5, which is the default
Don't discount being able to use features from newer versions of python
within Django itself.
- dicts are more performant
- dicts/kwargs/class attributes are ordered (cpython implementation detail
for 3.6 - allowing us to consider removing descriptor
I worry about the precedent we'd set if we made an exception for Debian,
because the next question would be "OK, can we have an exception for Red
Hat, too?" Keep in mind Red Hat currently sells up to fourteen years of
support for their RHEL platform.
So I think it's best to recognize that:
I'm not going to argue one way or the other, as it doesn't really affect me
either way. (I will say that Python 3.5 is no longer a supported version on
On the other hand, I will argue how supporting 3.5 might affect the
upcoming Django version. I've included my opinionated breakdown
Now that we've dropped Python 2, I personally wouldn't mind having the
policy be to support all supported versions of python (except 2.7) at the
time of each Django release. So Django would drop just after Python drops.
(The most recent version of Django (and maybe LTS too) should probably also
Also, if Django does participate in GSoC this year, they'll have an ideas page
for it eventually similar to something like this -
The best thing that you can do today to improve your chances is start
You received this
Mail list logo