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 suspect it would break, but we'd not guarantee that. (I do worry a bit about saying we support somebody else's EOL software...) Assuming that, there's a diagram in PEP 602 (on the Annual Release Cycle) that shows we'd essentially be on the hook for 5 Python versions forever. https://www.python.org/dev/peps/pep-0602/#the-testing-matrix If that's too many, how would something like "Django supports the latest 4 versions of Python" sound? This would mean dropping the oldest version ≈12 months before it reached end of life. (We'd have to think about mapping to our 8 month release cycle.) Kind Regards, Carlton -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/15cd90d9-559f-435d-a07c-724c9b4ac839n%40googlegroups.com.
