On Wed, 20 Jan 2021 at 16:19, Tim Graham <timogra...@gmail.com> wrote:
> 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). Yep, my error. Please read as intended rather than as written. I’ll trust your superpowers for that. 😃 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. > Yes, this is something to clarify while we’re here. Strong demand for the latest version is expected (given previous experience). It’s this point that we get into the possibly 6 versions though, which is a lot. Not quite sure what to say about that (recalling your earlier points). C. -- 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/CAJwKpyTFj9bm3SdPo5iu2g-AdYRZuGxodbz9L5XNV0CpA0Zeug%40mail.gmail.com.
