p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Small corrections to 1.3-alpha release notes (an unintended paragraph break, bad link, stray backtick, etc.). 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14523 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Gabriel Hurley 2010-11-11 08:01:03 +00:00
parent 0b25176ed8
commit 75a64d7a22
1 changed files with 12 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/releases/1.3-alpha-1.txt
View File

@ -31,16 +31,14 @@ Class-based views
Django 1.3 adds a framework that allows you to use a class as a view. Django 1.3 adds a framework that allows you to use a class as a view.
This means you can compose a view out of a collection of methods that This means you can compose a view out of a collection of methods that
can be subclassed and overridden to provide can be subclassed and overridden to provide analogs of all the old
function-based generic views have been provided, along with a completely
generic view base class that can be used as the basis for reusable
applications that can be easily extended.
Analogs of all the old function-based generic views have been See :doc:`the documentation on Class-based Generic Views
provided, along with a completely generic view base class that can be </topics/class-based-views>` for more details. There is also a document to
used as the basis for reusable applications that can be easily help you :doc:`convert your function-based generic views to class-based
extended.
See :doc:`the documentation on Generic Views</topics/generic-views>`
for more details. There is also a document to help you :doc:`convert
your function-based generic views to class-based
views</topics/generic-views-migration>`. views</topics/generic-views-migration>`.
Logging Logging
@ -129,7 +127,8 @@ To compensate for this, the focus of the Django 1.3 development
process has been on adding lots of smaller, long standing feature process has been on adding lots of smaller, long standing feature
requests. These include: requests. These include:
* Improved tools for accessing and manipulating the current Site. * Improved tools for accessing and manipulating the current Site via
:func:`django.contrib.sites.models.get_current_site`.
* A :class:`~django.test.client.RequestFactory` for mocking * A :class:`~django.test.client.RequestFactory` for mocking
requests in tests. requests in tests.
@ -274,7 +273,7 @@ be removed entirely.
For more details, see the documentation :doc:`Django's release process For more details, see the documentation :doc:`Django's release process
</internals/release-process>` and our :doc:`deprecation timeline </internals/release-process>` and our :doc:`deprecation timeline
</internals/deprecation>`.` </internals/deprecation>`.
``mod_python`` support ``mod_python`` support
~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~
@ -285,8 +284,8 @@ of active projects in its version control repositories, and its lead developer
has shifted all of his efforts toward the lighter, slimmer, more stable, and has shifted all of his efforts toward the lighter, slimmer, more stable, and
more flexible ``mod_wsgi`` backend. more flexible ``mod_wsgi`` backend.
If you are currently using the ``mod_python`` request handler, it is strongly If you are currently using the ``mod_python`` request handler, you are strongly
encouraged you redeploy your Django instances using :doc:`mod_wsgi encouraged to redeploy your Django instances using :doc:`mod_wsgi
</howto/deployment/modwsgi>`. </howto/deployment/modwsgi>`.
Function-based generic views Function-based generic views