summaryrefslogtreecommitdiff
path: root/docs/faq
diff options
context:
space:
mode:
authorLuke Plant <L.Plant.98@cantab.net>2010-07-05 17:19:52 +0000
committerLuke Plant <L.Plant.98@cantab.net>2010-07-05 17:19:52 +0000
commit9d0b9ad85e472dfdf6dc157e66b32e160b3c4643 (patch)
treee6c7e1627a328c8e1b7cdb5c05c1fe5ee9e49c2b /docs/faq
parent0f34c3dbf4544438833b3f0c5fd9670e5ffcceff (diff)
Doc updates missed in [13423]
Refs #13880 git-svn-id: http://code.djangoproject.com/svn/django/trunk@13425 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/faq')
-rw-r--r--docs/faq/install.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/faq/install.txt b/docs/faq/install.txt
index f20b2bc187..0139a82a67 100644
--- a/docs/faq/install.txt
+++ b/docs/faq/install.txt
@@ -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.