These release series no longer receive security updates or bug fixes. Supported versions policy for detailed guidelines about what fixes will be backported. These releases will get security and data lossįixes applied for a guaranteed period of time, typically three years. Latest patch release?” will always be "yes."Ĭertain feature releases will be designated as long-term support So the answer to "should I upgrade to the The associated feature release, unless this is impossible for security These releases will be 100% compatible with Patch releases (A.B.C, etc.) will be issued as needed, toįix bugs and/or security issues. These releases will contain new features, improvements to existing features, and such. Supported Versionsįeature releases (A.B, A.B+1, etc.) will happen roughly every eight months. Make sure you read the documentation that corresponds to the version of Django you’ve just installed.Īnd 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. See the installation guide for further instructions. This archive is updatedĮvery time we commit code. Get it using this shell command, which requires Git:Ī gzipped tarball of the development version. This is only for experienced users who want to try incoming changes and help identify bugs before an official release. The latest and greatest Django version is the one that’s in our Git repository (our revision-control system). Pip: pip install Django=4.2.3 Option 2: Get the latest development version Read theĤ.2.3 release notes, then install it with The latest official version is 4.2.3 (LTS). Here’s how to get it: Option 1: Get the latest official version The FAQ for the Python versions supported by each version of Django. We recommend using the latest version of Python 3. Django is available open-source under the
0 kommentar(er)
