install.txt 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102
  1. .. _faq-install:
  2. FAQ: Installation
  3. =================
  4. How do I get started?
  5. ---------------------
  6. #. `Download the code`_.
  7. #. Install Django (read the :ref:`installation guide <intro-install>`).
  8. #. Walk through the :ref:`tutorial <intro-tutorial01>`.
  9. #. Check out the rest of the :ref:`documentation <index>`, and `ask questions`_ if you
  10. run into trouble.
  11. .. _`Download the code`: http://www.djangoproject.com/download/
  12. .. _ask questions: http://www.djangoproject.com/community/
  13. What are Django's prerequisites?
  14. --------------------------------
  15. Django requires Python_, specifically any version of Python from 2.4
  16. through 2.6. No other Python libraries are required for basic Django
  17. usage.
  18. For a development environment -- if you just want to experiment with Django --
  19. you don't need to have a separate Web server installed; Django comes with its
  20. own lightweight development server. For a production environment, Django
  21. follows the WSGI_ spec, which means it can run on a variety of server
  22. platforms. See :ref:`Deploying Django <howto-deployment-index>` for some
  23. popular alternatives. Also, the `server arrangements wiki page`_ contains
  24. details for several deployment strategies.
  25. If you want to use Django with a database, which is probably the case, you'll
  26. also need a database engine. PostgreSQL_ is recommended, because we're
  27. PostgreSQL fans, and MySQL_, `SQLite 3`_, and Oracle_ are also supported.
  28. .. _Python: http://www.python.org/
  29. .. _WSGI: http://www.python.org/dev/peps/pep-0333/
  30. .. _server arrangements wiki page: http://code.djangoproject.com/wiki/ServerArrangements
  31. .. _PostgreSQL: http://www.postgresql.org/
  32. .. _MySQL: http://www.mysql.com/
  33. .. _`SQLite 3`: http://www.sqlite.org/
  34. .. _Oracle: http://www.oracle.com/
  35. Do I lose anything by using Python 2.4 versus newer Python versions, such as Python 2.5 or 2.6?
  36. -----------------------------------------------------------------------------------------------
  37. Not in the core framework. Currently, Django itself officially supports any
  38. version of Python from 2.4 through 2.6, inclusive. However, newer versions of
  39. Python are often faster, have more features, and are better supported.
  40. Third-party applications for use with Django are, of course, free to set their
  41. own version requirements.
  42. Over the next year or two Django will begin dropping support for older Python
  43. versions as part of a migration which will end with Django running on Python 3
  44. (see below for details).
  45. All else being equal, we recommend that you use the latest 2.x release
  46. (currently Python 2.6). This will let you take advantage of the numerous
  47. improvements and optimizations to the Python language since version 2.4, and
  48. will help ease the process of dropping support for older Python versions on
  49. the road to Python 3.
  50. Can I use Django with Python 2.3?
  51. ---------------------------------
  52. Django 1.1 (and earlier) supported Python 2.3. Django 1.2 and newer does not.
  53. We highly recommend you upgrade Python if at all possible, but Django 1.1 will
  54. continue to work on Python 2.3.
  55. Can I use Django with Python 3?
  56. -------------------------------
  57. Not at the moment. Python 3.0 introduced a number of
  58. backwards-incompatible changes to the Python language, and although
  59. these changes are generally a good thing for Python's future, it will
  60. be a while before most Python software catches up and is able to run
  61. on Python 3.0. For larger Python-based software like Django, the
  62. transition is expected to take at least a year or two (since it
  63. involves dropping support for older Python releases and so must be
  64. done gradually).
  65. In the meantime, Python 2.x releases will be supported and provided
  66. with bug fixes and security updates by the Python development team, so
  67. continuing to use a Python 2.x release during the transition should
  68. not present any risk.
  69. Will Django run under shared hosting (like TextDrive or Dreamhost)?
  70. -------------------------------------------------------------------
  71. See our `Django-friendly Web hosts`_ page.
  72. .. _`Django-friendly Web hosts`: http://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
  73. Should I use the official version or development version?
  74. ---------------------------------------------------------
  75. The Django developers improve Django every day and are pretty good about not
  76. checking in broken code. We use the development code (from the Subversion
  77. repository) directly on our servers, so we consider it stable. With that in
  78. mind, we recommend that you use the latest development code, because it
  79. generally contains more features and fewer bugs than the "official" releases.