mirror of
				https://github.com/django/django.git
				synced 2025-10-31 09:41:08 +00:00 
			
		
		
		
	Updated FAQ on Python versions to explain 2 vs 3.
Required the latest version for each Python series to minimize bookkeeping in the future.
This commit is contained in:
		| @@ -38,22 +38,6 @@ PostgreSQL fans, and MySQL_, `SQLite 3`_, and Oracle_ are also supported. | ||||
| .. _`SQLite 3`: http://www.sqlite.org/ | ||||
| .. _Oracle: http://www.oracle.com/ | ||||
|  | ||||
| Do I lose anything by using Python 2.6 versus newer Python versions, such as Python 2.7? | ||||
| ---------------------------------------------------------------------------------------- | ||||
|  | ||||
| Not in the core framework. Currently, Django itself officially supports | ||||
| Python 2.6 (2.6.5 or higher), 2.7, 3.2.3 or higher. However, newer versions of | ||||
| Python are often faster, have more features, and are better supported. If you | ||||
| use a newer version of Python you will also have access to some APIs that | ||||
| aren't available under older versions of Python. | ||||
|  | ||||
| Third-party applications for use with Django are, of course, free to set their | ||||
| own version requirements. | ||||
|  | ||||
| All else being equal, we recommend that you use the latest 2.7 or 3.x release. | ||||
| This will let you take advantage of the numerous improvements and optimizations | ||||
| to the Python language since version 2.6. | ||||
|  | ||||
| What Python version can I use with Django? | ||||
| ------------------------------------------ | ||||
|  | ||||
| @@ -65,20 +49,35 @@ Django version Python versions | ||||
| 1.2            2.4, 2.5, 2.6, 2.7 | ||||
| 1.3            2.4, 2.5, 2.6, 2.7 | ||||
| 1.4            2.5, 2.6, 2.7 | ||||
| 1.5            2.6.5, 2.7 and 3.2.3, 3.3 (experimental) | ||||
| **1.6**        **2.6.5, 2.7** and **3.2.3, 3.3** | ||||
| *1.7 (future)* *2.7, 3.3 (to be confirmed)* | ||||
| 1.5            2.6, 2.7 and 3.2, 3.3 (experimental) | ||||
| **1.6**        **2.6, 2.7** and **3.2, 3.3** | ||||
| *1.7 (future)* *2.7* and *3.2, 3.3* | ||||
| ============== =============== | ||||
|  | ||||
| Can I use Django with Python 3? | ||||
| ------------------------------- | ||||
| For a given series of Python versions, only the latest release is officially | ||||
| supported. For instance, at the time of writing (July 1st, 2013), the latest | ||||
| release in the 2.7 series is 2.7.5. | ||||
|  | ||||
| Yes, you can! | ||||
|  | ||||
| Django 1.5 introduced experimental support for Python 3.2.3 and above. | ||||
| What Python version should I use with Django? | ||||
| --------------------------------------------- | ||||
|  | ||||
| As of Django 1.6, Python 3 support is considered stable and you can safely use | ||||
| it in production. See also :doc:`/topics/python3`. | ||||
| it in production. See also :doc:`/topics/python3`. However, the community is | ||||
| still in the process of migrating third-party packages and applications to | ||||
| Python 3. | ||||
|  | ||||
| If you're starting a new project, and the dependencies you plan to use work on | ||||
| Python 3, you should use Python 3. If they don't, consider contributing to the | ||||
| porting efforts, or stick to Python 2. | ||||
|  | ||||
| Since newer versions of Python are often faster, have more features, and are | ||||
| better supported, all else being equal, we recommend that you use the latest | ||||
| 2.x.y or 3.x.y release. | ||||
|  | ||||
| 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. | ||||
|  | ||||
| Will Django run under shared hosting (like TextDrive or Dreamhost)? | ||||
| ------------------------------------------------------------------- | ||||
|   | ||||
		Reference in New Issue
	
	Block a user