Removed mentions of Python 2.3 support from the docs -- Django 1.2 drops...

What are Django's prerequisites?

--------------------------------

Django requires Python_, specifically any version of Python from 2.3

Django requires Python_, specifically any version of Python from 2.4

through 2.6. No other Python libraries are required for basic Django

usage.

.. _`SQLite 3`: http://www.sqlite.org/

.. _Oracle: http://www.oracle.com/

Do I lose anything by using Python 2.3 versus newer Python versions, such as Python 2.5?

Do I lose anything by using Python 2.4 versus newer Python versions, such as Python 2.5 or 2.6?

----------------------------------------------------------------------------------------

Not in the core framework. Currently, Django itself officially

supports any version of Python from 2.3 through 2.6,

supports any version of Python from 2.4 through 2.6,

inclusive. However, some add-on components may require a more recent

Python version; the ``django.contrib.gis`` component, for example,

requires at least Python 2.4, and third-party applications for use

for details). So if you're just starting out with Python, it's

recommended that you use the latest 2.x release (currently, Python

2.6). This will let you take advantage of the numerous improvements

and optimizations to the Python language since version 2.3, and will

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.0.

Can I use Django with Python 2.3?

---------------------------------

Django 1.1 (and earlier) supported Python 2.3. Django 1.2 and newer does not.

We highly recommend you upgrade Python if at all possible, but Django 1.1 will

continue to work on Python 2.3.

Can I use Django with Python 3.0?

---------------------------------

--------------

Being a Python Web framework, Django requires Python. It works with any Python

version from 2.3 to 2.6 (due to backwards

version from 2.4 to 2.6 (due to backwards

incompatibilities in Python 3.0, Django does not currently work with

Python 3.0; see :ref:`the Django FAQ <faq-install>` for more

information on supported Python versions and the 3.0 transition), but we recommend installing Python 2.5 or later. If you do so, you won't need to set up a database just yet: Python 2.5 or later includes a lightweight database called SQLite_.

    optional ``login_url`` argument, which lets you specify the URL for your

    login page (:setting:`settings.LOGIN_URL <LOGIN_URL>` by default).

    Example in Python 2.3 syntax::

        from django.contrib.auth.decorators import user_passes_test

        def my_view(request):

            # ...

        my_view = user_passes_test(lambda u: u.has_perm('polls.can_vote'), login_url='/login/')(my_view)

    Example in Python 2.4 syntax::

    For example::

        from django.contrib.auth.decorators import user_passes_test

    from django.views.decorators.vary import vary_on_headers

    # Python 2.3 syntax.

    def my_view(request):

        # ...

    my_view = vary_on_headers(my_view, 'User-Agent')

    # Python 2.4+ decorator syntax.

    @vary_on_headers('User-Agent')

    def my_view(request):

        # ...

    def front_page(request, blog_id):

        ...

Of course, if you're using Python 2.3 or prefer not to use the decorator

syntax, you can write the same code as follows, there is no difference::

    def front_page(request, blog_id):

        ...

    front_page = condition(last_modified_func=latest_entry)(front_page)

Shortcuts for only computing one value

======================================