mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-24 06:06:09 +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

10
docs/ref/models/fields.txt
View File

@@ -413,11 +413,6 @@ The admin represents this as an ``<input type="text">`` (a single-line input).
A :class:`CharField` that checks that the value is a valid e-mail address.
In Django 0.96, this doesn't accept :attr:`~CharField.max_length`; its
:class:`~CharField.max_length` is automatically set to 75. In the Django
development version, :class:`~CharField.max_length` is set to 75 by default, but
you can specify it to override default behavior.
``FileField``
-------------
@@ -577,11 +572,6 @@ A floating-point number represented in Python by a ``float`` instance.
The admin represents this as an ``<input type="text">`` (a single-line input).
**NOTE:** The semantics of :class:`FloatField` have changed in the Django
development version. See the `Django 0.96 documentation`_ for the old behavior.
.. _Django 0.96 documentation: http://www.djangoproject.com/documentation/0.96/model-api/#floatfield
``ImageField``
--------------

8
docs/ref/models/querysets.txt
View File

@@ -959,10 +959,10 @@ SQL equivalents::
SELECT ... WHERE id IS NULL;
.. versionchanged:: 1.0
The semantics of ``id__exact=None`` have
changed in the development version. Previously, it was (intentionally)
converted to ``WHERE id = NULL`` at the SQL level, which would never match
anything. It has now been changed to behave the same as ``id__isnull=True``.
The semantics of ``id__exact=None`` have changed in Django 1.0. Previously,
it was (intentionally) converted to ``WHERE id = NULL`` at the SQL level,
which would never match anything. It has now been changed to behave the
same as ``id__isnull=True``.
.. admonition:: MySQL comparisons