mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-23 21:59:11 +00:00
Code Issues 32 Releases Wiki Activity

[1.0.x] Fixed #9477 -- Removed and edited a bunch of references to "development

Browse Source 
version". Some were replaced with versionadded or versionchanged directives.
Other, more minor ones, were removed altogether.

Based on a patch from James Bennett.

Backport of r9454 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9455 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick
2008-11-15 05:56:01 +00:00
parent a4782f0581
commit c0feb2fad9
11 changed files with 30 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/topics/auth.txt
View File

@@ -320,8 +320,10 @@ Hashtype is either ``sha1`` (default), ``md5`` or ``crypt`` -- the algorithm
used to perform a one-way hash of the password. Salt is a random string used
to salt the raw password to create the hash. Note that the ``crypt`` method is
only supported on platforms that have the standard Python ``crypt`` module
available, and ``crypt`` support is only available in the Django development
version.
available.
.. versionadded:: 1.0
Support for the ``crypt`` module is new in Django 1.0.
For example::
@@ -626,7 +628,6 @@ The login_required decorator
def my_view(request):
# ...
In the Django development version,
:func:`~django.contrib.auth.decorators.login_required` also takes an
optional ``redirect_field_name`` parameter. Example::

4
docs/topics/forms/modelforms.txt
View File

@@ -77,9 +77,9 @@ the full list of conversions:
=============================== ========================================
.. note::
.. versionadded:: 1.0
The ``FloatField`` form field and ``DecimalField`` model and form fields
are new in the development version.
are new in Django 1.0.
As you might expect, the ``ForeignKey`` and ``ManyToManyField`` model field
types are special cases:

3
docs/topics/i18n.txt
View File

@@ -806,8 +806,7 @@ The view expects to be called via the ``POST`` method, with a ``language``
parameter set in request. If session support is enabled, the view
saves the language choice in the user's session. Otherwise, it saves the
language choice in a cookie that is by default named ``django_language``.
(The name can be changed through the ``LANGUAGE_COOKIE_NAME`` setting if you're
using the Django development version.)
(The name can be changed through the ``LANGUAGE_COOKIE_NAME`` setting.)
After setting the language choice, Django redirects the user, following this
algorithm:

12
docs/topics/testing.txt
View File

@@ -186,12 +186,12 @@ test utility is to find all the test cases (that is, subclasses of
``unittest.TestCase``) in ``models.py`` and ``tests.py``, automatically build a
test suite out of those test cases, and run that suite.
In the Django development version, there is a second way to define the test
suite for a module: if you define a function called ``suite()`` in either
``models.py`` or ``tests.py``, the Django test runner will use that function
to construct the test suite for that module. This follows the `suggested
organization`_ for unit tests. See the Python documentation for more details on
how to construct a complex test suite.
There is a second way to define the test suite for a module: if you define a
function called ``suite()`` in either ``models.py`` or ``tests.py``, the
Django test runner will use that function to construct the test suite for that
module. This follows the `suggested organization`_ for unit tests. See the
Python documentation for more details on how to construct a complex test
suite.
For more details about ``unittest``, see the `standard library unittest
documentation`_.