Link Search Menu Expand Document
Version Active Support Security Support Release
3.2 (LTS) Ends in 6 months and 4 weeks
(01 Dec 2021)
Ends in 2 years and 11 months
(01 Apr 2024)
3.1 Ended 1 month ago
(05 Apr 2021)
Ends in 6 months and 4 weeks
(01 Dec 2021)
3.0 Ended 9 months ago
(01 Aug 2020)
Ended 1 month and 5 days ago
(01 Apr 2021)
2.2 (LTS) Ended 1 year and 5 months ago
(01 Dec 2019)
Ends in 11 months
(01 Apr 2022)
2.1 Ended 2 years ago
(01 Apr 2019)
Ended 1 year and 5 months ago
(01 Dec 2019)
2.0 Ended 2 years and 9 months ago
(01 Aug 2018)
Ended 2 years ago
(01 Apr 2019)
1.11 (LTS) Ended 3 years and 5 months ago
(02 Dec 2017)
Ended 1 year ago
(01 Apr 2020)

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Feature releases (A.B, A.B+1, etc.) will happen roughly every eight months. These releases will contain new features, improvements to existing features, and such.

Patch releases (A.B.C, etc.) will be issued as needed, to fix bugs and/or security issues. These releases will be 100% compatible with the associated feature release, unless this is impossible for security reasons or to prevent data loss. So the answer to “should I upgrade to the latest patch release?” will always be “yes.”

Certain feature releases will be designated as long-term support (LTS) releases. These releases will get security and data loss fixes applied for a guaranteed period of time, typically three years.

See the supported versions policy for detailed guidelines about what fixes will be backported.

More information is available on the Django website.

You should be running one of the supported release numbers listed above in the rightmost column.

You can check the version that you are currently using by running:

python -c "import django; print(django.get_version())"

You can submit an improvement to this page by visiting GitHub. You will need to fork the website and submit a Pull Request.