From ae35d5178b4ec33b4615c548d596011160756a89 Mon Sep 17 00:00:00 2001 From: Christian Clauss Date: Fri, 15 Dec 2023 06:16:02 +0100 Subject: [PATCH] [5.0.x] Updated examples for 2.0+ release numbering in installation FAQ. Backport of 0d5e9a32eb5bd1201437519a3bda1fb4c4d06af9 from main --- docs/faq/install.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/faq/install.txt b/docs/faq/install.txt index 388350b2d8..01b5921357 100644 --- a/docs/faq/install.txt +++ b/docs/faq/install.txt @@ -63,9 +63,9 @@ download page `_. 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 ended -September 2017 and Django 1.8 LTS security support ended April 2018. Therefore -Django 1.8 is the last version to support Python 3.3. +version of Python ends. For example, Python 3.9 security support ends in +October 2025 and Django 4.2 LTS security support ends in April 2026. Therefore +Django 4.2 is the last version to support Python 3.9. What Python version should I use with Django? =============================================