--
Ticket URL: <https://code.djangoproject.com/ticket/30116>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/10864 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:1>
Comment (by Claude Paroz):
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?
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:2>
Comment (by Tim Graham):
If that's the consensus, I guess we should rewrite
[https://docs.djangoproject.com/en/dev/faq/install/#what-python-version-
can-i-use-with-django our policy about Python version support] and instead
base it on Debian (you made [https://groups.google.com/d/msg/django-
developers/4rbVKJYm8DI/TTh3i04pBQAJ the same argument] about Python 3.4
support).
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:3>
Comment (by Claude Paroz):
It's not a consensus at all for now, I'm just on the side on the very
conservative people wrt long time support software. Feel free to ignore me
if I'm on a small minority boat. I'm not vindictive :-)
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:4>
Comment (by Simon Charette):
Thanks for your input Claude. I also think we should stick to our
documented policy as well to be coherent with the previous releases.
I'm not too familiar with Debian's package policy but given 2.2 LTS is not
going away anytime soon nothing should prevent them from sticking to it
until Debian stable defaults to 3.6+?
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:5>
Comment (by Claude Paroz):
Yes, sure, it's more about people willing to contribute to Django master
will have to install a custom Python version in current Debian stable (the
next one should be out this summer).
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:6>
Comment (by Tim Graham):
I created a [https://groups.google.com/d/topic/django-
developers/YDJwI7uvgxU/discussion django-developers discussion] regarding
the Python version support policy.
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:7>
Comment (by Carlton Gibson):
There's not consensus to change the policy on the mailing list, so we can
push forward with this.
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:8>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"7e6b214ed34f5562dbd83cf54924a5b589a29715" 7e6b214]:
{{{
#!CommitTicketReference repository=""
revision="7e6b214ed34f5562dbd83cf54924a5b589a29715"
Fixed #30116 -- Dropped support for Python 3.5.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:9>
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"b711eafd2aabdf22e1d529bfb76dd8d3356d7000" b711eafd]:
{{{
#!CommitTicketReference repository=""
revision="b711eafd2aabdf22e1d529bfb76dd8d3356d7000"
Refs #30116 -- Removed unnecessary str() calls in CommonPasswordValidator.
open() and gzip.open() supports path-like objects since Python 3.6.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:10>
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"e0e88ceaaae4b27913cc9d3b48bf79c681605fba" e0e88cea]:
{{{
#!CommitTicketReference repository=""
revision="e0e88ceaaae4b27913cc9d3b48bf79c681605fba"
Refs #30116 -- Simplified stdout/stderr decoding with subprocess.run()'s
encoding argument.
The encoding argument has been available since Python 3.6.
https://docs.python.org/3/library/subprocess.html#subprocess.run
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:11>
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"d6aff369ad33457ae2355b5b210faf1c4890ff35" d6aff369]:
{{{
#!CommitTicketReference repository=""
revision="d6aff369ad33457ae2355b5b210faf1c4890ff35"
Refs #30116 -- Simplified regex match group access with
Match.__getitem__().
The method has been available since Python 3.6. The shorter syntax is
also marginally faster.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:12>
Comment (by GitHub <noreply@…>):
In [changeset:"4afaeb14c293725d7b2530788083fce1c120ff65" 4afaeb14]:
{{{
#!CommitTicketReference repository=""
revision="4afaeb14c293725d7b2530788083fce1c120ff65"
Refs #30116 -- Simplified tests related with dictionary order.
Dicts preserve order since Python 3.6.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30116#comment:13>