Hi Carlton, This chart doesn't look quite right for the policy you wrote. For example, I wouldn't expect Django 4.2 LTS (supported until April 2026) to support Python 3.8 (only supported until October 2024). It seems like this policy makes it more likely that the last Django version to support a Python would be a non-LTS rather than an LTS. Maybe that's fine.
It might also be helpful to clarify the backport policy for Python version support. Something like, "the latest stable version of Python will be supported in the latest stable version of Django (and the latest Django LTS)". For example, unlike your chart, I had Python 3.13 backported to 4.2 and 5.0. On Wednesday, January 20, 2021 at 3:21:44 AM UTC-5 carlton...@gmail.com wrote: > OK, so... > > Updating Tim's table to have "A version of Django will support current > Python versions who's EOL date is not before it's own EOL date" would give > us: > > Django Released End of life Support Python > Versions > 4.0 December 2021 April 2023 3.7, 3.8, 3.9, 3.10 > 4.1 August 2022 December 2023 3.8, 3.9, 3.10, 3.11 > (Oct 2022) > 4.2 LTS April 2023 April 2026 3.8, 3.9, 3.10, > 3.11, 3.12 (Oct 2023) > 5.0 December 2023 April 2025 3.9, 3.10, 3.11, > 3.12 > 5.1 August 2024 December 2025 3.10, 3.11, 3.12, 3.13 > (Oct 2024) > 5.2 LTS April 2025 April 2028 3.10, 3.11, > 3.12, 3.13, 3.14 (Oct 2025) > > Python Released End of life > 3.7 June 2018 June 2023 > 3.8 October 2019 October 2024 > 3.9 October 2020 October 2025 > 3.10 October 2021 October 2026 > 3.11 October 2022 October 2027 > 3.12 October 2023 October 2028 > 3.13 October 2024 October 2029 > 3.14 October 2025 October 2030 > > This looks like it would mean in general supporting 4 versions of Python > and 5 for the LTS. > The .1 and LTS would drop a version against the .0 > > I'd go for this, at least through the next cycle or so. > (Django 6.0 might look as if it's on the hook for the full 5 versions 🤔 > but I think we could revisit before then.) > > My concern is the paragraph in Tim's reply above that begins "Part of the > rationale for dropping Python versions after an LTS is was to avoid getting > "stranded" on a non-LTS version of Django." — I'm not sure we can do > anything there apart from maybe say that people have to update their > Python. (I'm not sure we have the capacity or duty to do more if folks are > lingering here?) > > How do we decide? Mariusz has opened the PR to drop both 3.6 and 3.7 > support. > https://github.com/django/django/pull/13915 > We can merge the 3.6 stuff, but it would be nice to settle this. > (I don't know) > > Kind Regards, > > Carlton > > > On Tuesday, 19 January 2021 at 20:36:21 UTC+1 Claude Paroz wrote: > >> When I see that Python 3.7 will be supported the whole time of the 4.0 >> support period, it's enough for me. For the rest, let the people choose and >> see by themselves through the support graphs what their interest is. I >> think we should stop patronizing developers. >> >> Claude >> > -- 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 django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a616ce7b-2096-4800-957b-1f92e1a525a4n%40googlegroups.com.
