FAQ: Installation

Install Django (read the installation guide).
Walk through the .

For a development environment – if you just want to experiment with Django – you don’t need to have a separate web server installed or database server.

Django comes with its own lightweight development server. For a production environment, Django follows the WSGI spec, , which means it can run on a variety of web servers. See Deploying Django for more information.

For each version of Python, only the latest micro release (A.B.C) is officially supported. You can find the latest micro version for each series on the .

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.

You don’t lose anything in Django by using an older release, but you don’t take advantage of the improvements and optimizations in newer Python releases. Third-party applications for use with Django are free to set their own version requirements.

Generally, if you’re using code in production, you should be using a stable release. The Django project publishes a full stable release every nine months or so, with bugfix updates in between. These stable releases contain the API that is covered by our backwards compatibility guarantees; if you write code against stable releases, you shouldn’t have any problems upgrading when the next official version is released.