Upgrades and deprecations
Upgrade Django 3.2 to the Latest LTS: Route, Python and Dates
In short
Take Django 3.2 to 4.2 and then to 5.2, one LTS at a time. Django 5.2 is the newest released LTS and gets security fixes until April 2028. Django 4.2 lost its extended support on 7 April 2026, so it is a stop on the way, not a destination. The next LTS, 6.2, is planned for April 2027.
Where does each Django release stand on 19 November 2026?
Django's download page lists the latest feature release as 6.1, with 6.1.3 as its newest patch. The newest LTS that has actually shipped is 5.2. Django 6.2, the next LTS, appears only on the future roadmap with an April 2027 release date.
The Python column below is each release's own Python compatibility statement. Django 3.2 and 4.2 are both past extended support, so any site still on 3.2 has gone more than two and a half years without security fixes from Django.
| Release | Python stated by Django | Mainstream support ends | Extended support ends | Status |
|---|---|---|---|---|
| 3.2 LTS | 3.6 - 3.10 | 7 December 2021 | 1 April 2024 | Ended |
| 4.2 LTS | 3.8 - 3.12 | 4 December 2023 | 7 April 2026 | Ended |
| 5.2 LTS | 3.10 - 3.14 | 3 December 2025 | April 2028 | Security and data-loss fixes only |
| 6.1 | 3.12 - 3.15 | April 2027 | December 2027 | Latest release, not an LTS |
| 6.2 LTS | 3.12 - 3.15 | December 2027 | April 2030 | Planned for April 2027 |
Checked against: source 1, source 3, source 6, source 9, source 11, source 12
Does Django recommend jumping from 3.2 straight to 5.2?
No. The official upgrade guide says that when you cross more than one feature version, it is usually easier to go through each one in turn. It adds that the same incremental approach is recommended from one LTS to the next, and that you should use the latest patch release of each step.
The guide's own example is 5.2 LTS to 6.2 LTS, but the rule is stated generally. For this route that means 3.2.25, then 4.2.30, then 5.2.19, which are the latest patches the download page lists. Read the release notes of every final release between your version and the target, not only the LTS ones.
I would deploy only at the LTS stops and use the feature releases between them as test checkpoints. The guide also tells you to turn on deprecation warnings before each step, because Python hides them by default.
Which Python version can carry each hop?
This is the part the Django pages leave you to join up yourself. The Python ranges of two neighbouring LTS releases overlap only in a narrow band, and the first overlap is entirely unsupported Python.
| Hop | Python versions both ends accept | Status of those Pythons on 19 Nov 2026 |
|---|---|---|
| 3.2 to 4.2 | 3.8, 3.9, 3.10 | All three have reached end of life (3.10 on 1 October 2026) |
| 4.2 to 5.2 | 3.10, 3.11, 3.12 | 3.10 ended; 3.11 security fixes to October 2027; 3.12 to October 2028 |
Checked against: source 3, source 6, source 9, source 13, source 14
What is the safest Python plan across the whole route?
Django 4.0 notes that the 3.2 series is the last to support Python 3.6 and 3.7, and Django 3.2 itself stops at Python 3.10. I would therefore move the 3.2 project to Python 3.10 first, make the hop to 4.2, and then change Python again.
Django 4.2 accepts Python 3.12, so the second Python move can happen on 4.2 before the hop to 5.2. Python 3.12 sits inside the ranges of 4.2, 5.2, 6.1 and 6.2, and its security support runs to October 2028, past the April 2028 end of Django 5.2's extended support. Python 3.11 also works for 4.2 and 5.2, but Django 6.0 and later require 3.12 or newer.
Django 5.0 notes that the 4.2.x series is the last to support Python 3.8 and 3.9, and Django 6.0 notes the same for 5.2.x and Python 3.10 and 3.11.
Checked against: source 3, source 4, source 6, source 7, source 9, source 10, source 11, source 12, source 13
Which removals in the release notes tend to block each hop?
Each release notes page has a features removed section that lists code deleted after its deprecation period. The items below are the ones I would grep for first. The lists are partial; read the full pages.
- 3.2 to 4.0:
urlquote(),force_text(),ugettext(),is_safe_url(),django.conf.urls.url(), theifequalandifnotequaltags,NullBooleanField,HttpRequest.is_ajax()and the postgresJSONFieldare removed.CSRF_TRUSTED_ORIGINSvalues must now include the scheme, and PostgreSQL 10 becomes the minimum. If forms start returning 403 after this step, see this fix page. - 4.0 to 4.1:
default_app_configand theMemcachedCachebackend are removed. PostgreSQL 10 and MariaDB 10.2 support is dropped. - 4.1 to 4.2: the 4.2 notes have no features-removed section. They drop MariaDB 10.3, MySQL 5.7 and PostgreSQL 11, so the database floor becomes PostgreSQL 12 and MySQL 8.
UserCreationFormnow rejects usernames that differ only in case. - 4.2 to 5.0: the
USE_L10Nsetting, pytz support,PickleSerializerand logging out through a GET request are removed, andUSE_TZnow defaults toTrue. - 5.0 to 5.1:
index_together, theDEFAULT_FILE_STORAGEandSTATICFILES_STORAGEsettings,make_random_password()and the SHA1 password hashers are removed. - 5.1 to 5.2: no features-removed section. PostgreSQL 13 support is dropped, so the floor is PostgreSQL 14, and MySQL connections now default to
utf8mb4.
Checked against: source 4, source 5, source 6, source 7, source 8, source 9
Should the route stop at 5.2 or wait for 6.2?
I would land on 5.2 now. Waiting for 6.2 would leave a 3.2 site without Django security fixes until at least April 2027. Django 6.0 and 6.1 are not LTS releases, and 6.0 loses extended support in April 2027, the same month 6.2 is planned.
The upgrade guide says that from 2028 every feature release gets three years of support, so the LTS label disappears after 6.2. The hop from 5.2 to 6.2 needs Python 3.12 or newer, which the plan above already covers.
This page compares vendor documents. It does not cover your third-party packages, your database data or your deployment. The guide itself warns that some dependencies may not support a new Django version yet, and that is the check I cannot do for you.
What else do people ask?
Is Django 4.2 still supported?
Not by Django. Its extended support ended on 7 April 2026 according to the download page, so use it only as a stop on the way to 5.2.
Which Python should I use while upgrading from Django 3.2?
Django 3.2 accepts Python up to 3.10 and Django 4.2 accepts up to 3.12. Python 3.10 is the only bridge for the first hop and it has reached end of life, so I would move to 3.12 right after reaching 4.2.
Sources
- Django download page, supported versions and roadmap, fetched 2026-11-19
- How to upgrade Django to a newer version, fetched 2026-11-19
- Django 3.2 release notes, Python compatibility, fetched 2026-11-19
- Django 4.0 release notes, removals and backwards incompatible changes, fetched 2026-11-19
- Django 4.1 release notes, removals and dropped databases, fetched 2026-11-19
- Django 4.2 release notes, backwards incompatible changes, fetched 2026-11-19
- Django 5.0 release notes, removals and Python compatibility, fetched 2026-11-19
- Django 5.1 release notes, features removed, fetched 2026-11-19
- Django 5.2 release notes, LTS statement and backwards incompatible changes, fetched 2026-11-19
- Django 6.0 release notes, Python compatibility, fetched 2026-11-19
- Django 6.1 release notes, Python compatibility and support dates, fetched 2026-11-19
- Django 6.2 release notes (under development), LTS statement and Python compatibility, fetched 2026-11-19
- Python developer guide, status of Python versions, fetched 2026-11-19
- endoflife.date, Python release cycles, fetched 2026-11-19
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. This page compares vendor documents I fetched on 19 Nov 2026 (the Django download page, upgrade guide and release notes, and the Python developer guide). I did not run these upgrades for it. It does not cover third-party packages, your data migrations or production rollout. Found a mistake? Tell me.