install.txt 4.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. FAQ: Installation
  2. =================
  3. How do I get started?
  4. ---------------------
  5. #. `Download the code`_.
  6. #. Install Django (read the :doc:`installation guide </intro/install>`).
  7. #. Walk through the :doc:`tutorial </intro/tutorial01>`.
  8. #. Check out the rest of the :doc:`documentation </index>`, and `ask questions`_ if you
  9. run into trouble.
  10. .. _`Download the code`: https://www.djangoproject.com/download/
  11. .. _ask questions: https://www.djangoproject.com/community/
  12. What are Django's prerequisites?
  13. --------------------------------
  14. Django requires Python, specifically Python 2.7 or 3.2 and above. No other
  15. Python libraries are required for basic Django usage.
  16. For a development environment -- if you just want to experiment with Django --
  17. you don't need to have a separate Web server installed; Django comes with its
  18. own lightweight development server. For a production environment, Django follows
  19. the WSGI spec, :pep:`3333`, which means it can run on a variety of server
  20. platforms. See :doc:`Deploying Django </howto/deployment/index>` for some
  21. popular alternatives. Also, the `server arrangements wiki page`_ contains
  22. details for several deployment strategies.
  23. If you want to use Django with a database, which is probably the case, you'll
  24. also need a database engine. PostgreSQL_ is recommended, because we're
  25. PostgreSQL fans, and MySQL_, `SQLite 3`_, and Oracle_ are also supported.
  26. .. _Python: http://www.python.org/
  27. .. _server arrangements wiki page: https://code.djangoproject.com/wiki/ServerArrangements
  28. .. _PostgreSQL: http://www.postgresql.org/
  29. .. _MySQL: http://www.mysql.com/
  30. .. _`SQLite 3`: http://www.sqlite.org/
  31. .. _Oracle: http://www.oracle.com/
  32. What Python version can I use with Django?
  33. ------------------------------------------
  34. ============== ===============
  35. Django version Python versions
  36. ============== ===============
  37. 1.0 2.3, 2.4, 2.5, 2.6
  38. 1.1 2.3, 2.4, 2.5, 2.6
  39. 1.2 2.4, 2.5, 2.6, 2.7
  40. 1.3 2.4, 2.5, 2.6, 2.7
  41. 1.4 2.5, 2.6, 2.7
  42. 1.5 2.6, 2.7 and 3.2, 3.3 (experimental)
  43. 1.6 2.6, 2.7 and 3.2, 3.3
  44. **1.7** **2.7** and **3.2, 3.3**
  45. ============== ===============
  46. For a given series of Python versions, only the latest release is officially
  47. supported. For instance, at the time of writing (July 1st, 2013), the latest
  48. release in the 2.7 series is 2.7.5.
  49. What Python version should I use with Django?
  50. ---------------------------------------------
  51. As of Django 1.6, Python 3 support is considered stable and you can safely use
  52. it in production. See also :doc:`/topics/python3`. However, the community is
  53. still in the process of migrating third-party packages and applications to
  54. Python 3.
  55. If you're starting a new project, and the dependencies you plan to use work on
  56. Python 3, you should use Python 3. If they don't, consider contributing to the
  57. porting efforts, or stick to Python 2.
  58. Since newer versions of Python are often faster, have more features, and are
  59. better supported, all else being equal, we recommend that you use the latest
  60. 2.x.y or 3.x.y release.
  61. You don't lose anything in Django by using an older release, but you don't take
  62. advantage of the improvements and optimizations in newer Python releases.
  63. Third-party applications for use with Django are, of course, free to set their
  64. own version requirements.
  65. Will Django run under shared hosting (like TextDrive or Dreamhost)?
  66. -------------------------------------------------------------------
  67. See our `Django-friendly Web hosts`_ page.
  68. .. _`Django-friendly Web hosts`: https://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
  69. Should I use the stable version or development version?
  70. -------------------------------------------------------
  71. Generally, if you're using code in production, you should be using a
  72. stable release. The Django project publishes a full stable release
  73. every nine months or so, with bugfix updates in between. These stable
  74. releases contain the API that is covered by our backwards
  75. compatibility guarantees; if you write code against stable releases,
  76. you shouldn't have any problems upgrading when the next official
  77. version is released.