Install Django (read the installation guide).
Walk through the tutorial.
Check out the rest of the documentation, and ask questions if you\nrun into trouble.
Django requires Python. See the table in the next question for the versions of\nPython that work with each version of Django. Other Python libraries may be\nrequired for some uses, but you’ll receive an error about it as they’re needed.
\nFor a development environment – if you just want to experiment with Django –\nyou don’t need to have a separate Web server installed; Django comes with its\nown lightweight development server. For a production environment, Django follows\nthe WSGI spec, PEP 3333, which means it can run on a variety of server\nplatforms. See Deploying Django for some\npopular alternatives.
\nIf you want to use Django with a database, which is probably the case, you’ll\nalso need a database engine. PostgreSQL is recommended, because we’re\nPostgreSQL fans, and MySQL, SQLite 3, and Oracle are also supported.
\nDjango version | \nPython versions | \n
|---|---|
1.8 | \n2.7, 3.2 (until the end of 2016), 3.3, 3.4, 3.5 | \n
1.9, 1.10 | \n2.7, 3.4, 3.5 | \n
For each version of Python, only the latest micro release (A.B.C) is officially\nsupported. You can find the latest micro version for each series on the Python\ndownload page.
\nTypically, we will support a Python version up to and including the first\nDjango LTS release whose security support ends after security support for that\nversion of Python ends. For example, Python 3.3 security support ends September\n2017 and Django 1.8 LTS security support ends April 2018. Therefore Django 1.8\nis the last version to support Python 3.3.
\nAs of Django 1.6, Python 3 support is considered stable and you can safely use\nit in production. See also Porting to Python 3. However, the community is\nstill in the process of migrating third-party packages and applications to\nPython 3.
\nIf you’re starting a new project, and the dependencies you plan to use work on\nPython 3, you should use Python 3. If they don’t, consider contributing to the\nporting efforts, or stick to Python 2.
\nSince newer versions of Python are often faster, have more features, and are\nbetter supported, all else being equal, we recommend that you use the latest\n2.x.y or 3.x.y release.
\nYou don’t lose anything in Django by using an older release, but you don’t take\nadvantage of the improvements and optimizations in newer Python releases.\nThird-party applications for use with Django are, of course, free to set their\nown version requirements.
\nGenerally, if you’re using code in production, you should be using a\nstable release. The Django project publishes a full stable release\nevery nine months or so, with bugfix updates in between. These stable\nreleases contain the API that is covered by our backwards\ncompatibility guarantees; if you write code against stable releases,\nyou shouldn’t have any problems upgrading when the next official\nversion is released.
\n