mirror of
https://github.com/django/django.git
synced 2025-08-30 23:37:50 +00:00
Doc updates missed in [13423]
Refs #13880 git-svn-id: http://code.djangoproject.com/svn/django/trunk@13425 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
0f34c3dbf4
commit
9d0b9ad85e
2 changed files with 3 additions and 3 deletions
|
@ -46,7 +46,7 @@ Do I lose anything by using Python 2.4 versus newer Python versions, such as Pyt
|
|||
-----------------------------------------------------------------------------------------------
|
||||
|
||||
Not in the core framework. Currently, Django itself officially supports any
|
||||
version of Python from 2.4 through 2.6, inclusive. However, newer versions of
|
||||
version of Python from 2.4 through 2.7, inclusive. However, newer versions of
|
||||
Python are often faster, have more features, and are better supported.
|
||||
Third-party applications for use with Django are, of course, free to set their
|
||||
own version requirements.
|
||||
|
@ -56,7 +56,7 @@ versions as part of a migration which will end with Django running on Python 3
|
|||
(see below for details).
|
||||
|
||||
All else being equal, we recommend that you use the latest 2.x release
|
||||
(currently Python 2.6). This will let you take advantage of the numerous
|
||||
(currently Python 2.7). This will let you take advantage of the numerous
|
||||
improvements and optimizations to the Python language since version 2.4, and
|
||||
will help ease the process of dropping support for older Python versions on
|
||||
the road to Python 3.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue