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 counters)
- fstrings
- type annotations (something some people are quite in favour of)
- async comprehensions and generators (less important for Django right now 
- may be more important for Channels)
- secrets module
- pathlib
- descriptor improvements (set_name, __init_subclass__)

I'm more in favour of maintaining the existing policy than playing 
favourites with distro support, but not strongly so. The LTS Django is 
already covering Python 3.5 for 18 months **longer** than the EOL. I don't 
think the newest versions of Django need to be so concerned with distro 

On Wednesday, 23 January 2019 02:03:54 UTC+11, Federico Capoano wrote:
> 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 
> python version on many linux platforms right now, we will make the life of 
> our users and developers harder.
> I don't understand the reason for doing so, if we have to do it for a good 
> reason, like a security issue, or because django has to take advantage of 
> features that are available only from python 3.6 onwards, I would be in 
> favour, but if we have to do it only because the policy says so, without 
> any other advantage, I would amend the policy.
> My 2 cents.
> Thanks for your hard work maintaining django
> Federico 
> On Monday, January 21, 2019 at 10:56:40 AM UTC-5, Tim Graham wrote:
>> When deciding when to drop support for Python 2 in Django, there was 
>> consensus to adopt this Python version support policy [0]: "Typically, we 
>> will support a Python version up to and including the first Django LTS 
>> release whose security support ends after security support for that version 
>> of Python ends. For example, Python 3.3 security support ends September 
>> 2017 and Django 1.8 LTS security support ends April 2018. Therefore Django 
>> 1.8 is the last version to support Python 3.3."
>> Since then, we didn't abide by this policy when dropping Python 3.4, 
>> mainly because Debian stable still used Python 3.4 at the time and Claude 
>> argued that some people like him would have difficulty contributing to 
>> Django if they had to install another version of Python [1].
>> Based on the policy, it's time to drop support for Python 3.5 in the 
>> master branch (Django 3.0) -- with Django 2.2 LTS supported until April 
>> 2022 and Python 3.5 supported until September 2020). I created a ticket [2] 
>> and PR [3] for dropping support for Python 3.5 [2], however, Claude 
>> commented, "I'm not so enthusiast to drop Python 3.5 now (it is still the 
>> default version in Debian stable). Couldn't this be done in Django 3.1 
>> instead?"
>> Are you in favor of amending the Python support version policy to account 
>> for the Python version in Debian stable?
>> [0] 
>> [1] 
>> [2]
>> [3]

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 post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to