Skip to content
This repository has been archived by the owner on Nov 25, 2017. It is now read-only.

Commit

Permalink
Merge pull request #22 from eikonomega/master
Browse files Browse the repository at this point in the history
Updated Chapter 2: Admonition 'Django and Python 3.0'
  • Loading branch information
jacobian committed Apr 14, 2013
2 parents 5bbaabe + a80f2aa commit 138d953
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions chapter02.rst
Expand Up @@ -34,15 +34,15 @@ features you might like to use in your applications. Plus, certain third-party
Django add-ons that you might want to use might require a version newer than
Python 2.5, so using a later version of Python keeps your options open.

.. admonition:: Django and Python 3.0
.. admonition:: Django and Python 3.x

At the time of writing, Python 3.0 had been released, but Django
only supported it experimentally. Python 3.0 introduced a
substantial number of backwards-incompatible changes to the
At the time of writing, Python 3.3 has been released, but Django
only supports it experimentally. This is because the Python 3.x series
introduces a substantial number of backwards-incompatible changes to the
language itself, and, as a result, many major Python libraries and
frameworks, including Django, had not yet caught up.
frameworks, including Django (as of version 1.4), have not yet caught up.

Django 1.5 will support Python 2.6, 2.7, and 3.2. However,
Django 1.5 is slated to support Python 2.6, 2.7, and 3.2. However,
support for Python 3.2 is considered a "preview", which means the
Django developers are not yet confident enough to promise
stability in production. For that, they suggest you wait until
Expand Down Expand Up @@ -502,4 +502,4 @@ What's Next?
Now that you have everything installed and the development server running,
you're ready to :doc: learn the basics `Chapter 3`_, of serving Web pages with Django.

.. _Chapter 3: chapter03.rst/
.. _Chapter 3: chapter03.rst/

0 comments on commit 138d953

Please sign in to comment.