123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687 |
- =================
- FAQ: Installation
- =================
- How do I get started?
- =====================
- #. `Download the code`_.
- #. Install Django (read the :doc:`installation guide </intro/install>`).
- #. Walk through the :doc:`tutorial </intro/tutorial01>`.
- #. Check out the rest of the :doc:`documentation </index>`, and `ask questions`_ if you
- run into trouble.
- .. _`Download the code`: https://www.djangoproject.com/download/
- .. _ask questions: https://www.djangoproject.com/community/
- What are Django's prerequisites?
- ================================
- Django requires Python. See the table in the next question for the versions of
- Python that work with each version of Django. Other Python libraries may be
- required for some uses, but you'll receive an error about it as they're needed.
- For a development environment -- if you just want to experiment with Django --
- you don't need to have a separate Web server installed; Django comes with its
- own lightweight development server. For a production environment, Django follows
- the WSGI spec, :pep:`3333`, which means it can run on a variety of server
- platforms. See :doc:`Deploying Django </howto/deployment/index>` for some
- popular alternatives.
- If you want to use Django with a database, which is probably the case, you'll
- also need a database engine. PostgreSQL_ is recommended, because we're
- PostgreSQL fans, and MySQL_, `SQLite 3`_, and Oracle_ are also supported.
- .. _Python: https://www.python.org/
- .. _PostgreSQL: https://www.postgresql.org/
- .. _MySQL: https://www.mysql.com/
- .. _`SQLite 3`: https://www.sqlite.org/
- .. _Oracle: https://www.oracle.com/
- .. _faq-python-version-support:
- What Python version can I use with Django?
- ==========================================
- ============== ===============
- Django version Python versions
- ============== ===============
- 1.11 2.7, 3.4, 3.5, 3.6
- 2.0 3.4, 3.5, 3.6, 3.7
- 2.1, 2.2 3.5, 3.6, 3.7
- ============== ===============
- 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 `Python
- download page <https://www.python.org/downloads/>`_.
- 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 ends September
- 2017 and Django 1.8 LTS security support ends April 2018. Therefore Django 1.8
- is the last version to support Python 3.3.
- What Python version should I use with Django?
- =============================================
- Python 3 is recommended. Django 1.11 is the last version to support Python 2.7.
- Support for Python 2.7 and Django 1.11 ends in 2020.
- Since newer versions of Python are often faster, have more features, and are
- better supported, the latest version of Python 3 is recommended.
- 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, of course, free to set their
- own version requirements.
- Should I use the stable version or development version?
- =======================================================
- 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.
|