Re: Revisiting Python support for after Django 3.2 LTS

Thanks again Tim. I really appreciate your insight. On Tue, 24 Nov 2020 at 19:07, Tim Graham wrote: > That would be a heavy stick whereas there's already been some hesitance > here to the "carrot" argument of the current policy which restricts older > Python users to a Django LTS. > [...] > I

Re: Revisiting Python support for after Django 3.2 LTS

Dropping support for Python versions as they go EOL in existing Django releases would be disruptive. Distros "support" Python versions longer than the PSF does. If a Django version inadvertently breaks compatibility with an old version of Python because we stop testing with it, we'll get bug

Request for Comment: settings growth configuring Email Backend.

Hi all. Can I ask for guidance/comments please? Ticket 31885 Update SMTP Email Backend to use an SSLContext came in for which there's a PR adding `EMAIL_SSL_CAFILE` settings to match the existing

Re: Revisiting Python support for after Django 3.2 LTS

I think Redhat realized that they have old versions and this is not going to fly well during the lifetime of their system. This is why they introduced modules in v8 and strongly pushing podman. That said, it is a major hurdle for many companies if upstream drops support for $x (be that in

Re: Revisiting Python support for after Django 3.2 LTS

Hi Tim. Thanks for the breakdown, and context on the rationale. Do you think we can drop support for Python versions as they go EOL? i.e. for Django 2.2 we COULD HAVE stopped testing against Python 3.5 when it went EOL earlier this year. Given the backport policy, there's no reason to