Download
Django is available open-source under the BSD license. We recommend using the latest version of Python 3. The last version to support Python is Django LTS. See the FAQ for the Python versions supported by each version of Django. Here’s how to get it:
Option 1: Get the latest official version
The latest official version is Read the release notes, then install it with pip:
Option 2: Get the latest development version
The latest and greatest Django version is the one that’s in our Git repository (our revision-control system). This is only for experienced users who want to try incoming changes and help identify bugs before an official release. Get it using this shell command, which requires Git:
You can also download a gzipped tarball of the development version. This archive is updated every time we commit code.
After you get it
See the installation guide for further instructions. Make sure you read the documentation that corresponds to the version of Django you’ve just installed.
And be sure to sign up for the django-users mailing list, where other Django users and the Django developers themselves all hang out to help each other.
Supported Versions
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 % 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.
| Release Series | Latest Release | End of mainstream support1 | End of extended support2 |
|---|---|---|---|
| April | December | ||
| August, | April, | ||
| LTS | December 2, | April | |
| April 1, | December 2, | ||
| August 1, | April 1, | ||
| LTS 3 | December 2, | April 1, | |
| April 4, | December 2, | ||
| August 1, | April 4, | ||
| LTS | December 1, | April 1, | |
| April 1, | December 1, | ||
| September 2, | April 1, | ||
| November 6, | September 2, | ||
| LTS | February 26, | October 1, | |
| March 23, | February 26, |
Here's what the future roadmap looks like:
| Release Series | Release Date | End of mainstream support1 | End of extended support2 |
|---|---|---|---|
| LTS | April | December | April |
| December | August | April | |
| August | April | December | |
| LTS | April | December | April |
[1] Security fixes, data loss bugs, crashing bugs, major functionality bugs in newly-introduced features, and regressions from older versions of Django.
[2] Security fixes and data loss bugs.
[3] Last version to support Python
For the impatient:
Which version is better?
We improve Django almost every day and are pretty good about keeping the code stable. Thus, using the latest development code is a safe and easy way to get access to new features as they’re added. If you choose to follow the development version, keep in mind that there will occasionally be backwards-incompatible changes. You’ll want to pay close attention to the commits by watching Django on GitHub or subscribing to django-updates.
If you’re just looking for a stable deployment target and don’t mind waiting for the next release, you’ll want to stick with the latest official release (which will always include detailed notes on any changes you’ll need to make while upgrading).
-
-