mirror of
https://github.com/django/django.git
synced 2025-10-17 13:58:24 +00:00
Fixed #14000 - remove versionadded/changed tags for Django 1.0 and 1.1
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15055 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
00c554f89e
commit
2ea93f9327
58 changed files with 49 additions and 591 deletions
|
@ -195,9 +195,6 @@ it, you can access the clean data via its ``cleaned_data`` attribute::
|
|||
>>> f.cleaned_data
|
||||
{'cc_myself': True, 'message': u'Hi there', 'sender': u'foo@example.com', 'subject': u'hello'}
|
||||
|
||||
.. versionchanged:: 1.0
|
||||
The ``cleaned_data`` attribute was called ``clean_data`` in earlier releases.
|
||||
|
||||
Note that any text-based field -- such as ``CharField`` or ``EmailField`` --
|
||||
always cleans the input into a Unicode string. We'll cover the encoding
|
||||
implications later in this document.
|
||||
|
@ -680,8 +677,6 @@ by a ``Widget``::
|
|||
Binding uploaded files to a form
|
||||
--------------------------------
|
||||
|
||||
.. versionadded:: 1.0
|
||||
|
||||
Dealing with forms that have ``FileField`` and ``ImageField`` fields
|
||||
is a little more complicated than a normal form.
|
||||
|
||||
|
|
|
@ -230,8 +230,6 @@ fields. We've specified ``auto_id=False`` to simplify the output::
|
|||
``error_messages``
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. versionadded:: 1.0
|
||||
|
||||
.. attribute:: Field.error_messages
|
||||
|
||||
The ``error_messages`` argument lets you override the default messages that the
|
||||
|
@ -303,11 +301,6 @@ For each field, we describe the default widget used if you don't specify
|
|||
the field has ``required=True``.
|
||||
* Error message keys: ``required``
|
||||
|
||||
.. versionchanged:: 1.0
|
||||
The empty value for a ``CheckboxInput`` (and hence the standard
|
||||
``BooleanField``) has changed to return ``False`` instead of ``None`` in
|
||||
the Django 1.0.
|
||||
|
||||
.. note::
|
||||
|
||||
Since all ``Field`` subclasses have ``required=True`` by default, the
|
||||
|
@ -411,10 +404,6 @@ If no ``input_formats`` argument is provided, the default input formats are::
|
|||
'%B %d %Y', '%B %d, %Y', # 'October 25 2006', 'October 25, 2006'
|
||||
'%d %B %Y', '%d %B, %Y', # '25 October 2006', '25 October, 2006'
|
||||
|
||||
.. versionchanged:: 1.1
|
||||
The ``DateField`` previously used a ``TextInput`` widget by default. It now
|
||||
uses a ``DateInput`` widget.
|
||||
|
||||
``DateTimeField``
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
@ -446,14 +435,9 @@ If no ``input_formats`` argument is provided, the default input formats are::
|
|||
'%m/%d/%y %H:%M', # '10/25/06 14:30'
|
||||
'%m/%d/%y', # '10/25/06'
|
||||
|
||||
.. versionchanged:: 1.0
|
||||
The ``DateTimeField`` used to use a ``TextInput`` widget by default. This has now changed.
|
||||
|
||||
``DecimalField``
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
.. versionadded:: 1.0
|
||||
|
||||
.. class:: DecimalField(**kwargs)
|
||||
|
||||
* Default widget: ``TextInput``
|
||||
|
@ -506,8 +490,6 @@ given length.
|
|||
``FileField``
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
.. versionadded:: 1.0
|
||||
|
||||
.. class:: FileField(**kwargs)
|
||||
|
||||
* Default widget: ``ClearableFileInput``
|
||||
|
@ -526,8 +508,6 @@ When you use a ``FileField`` in a form, you must also remember to
|
|||
``FilePathField``
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. versionadded:: 1.0
|
||||
|
||||
.. class:: FilePathField(**kwargs)
|
||||
|
||||
* Default widget: ``Select``
|
||||
|
@ -572,8 +552,6 @@ These control the range of values permitted in the field.
|
|||
``ImageField``
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
.. versionadded:: 1.0
|
||||
|
||||
.. class:: ImageField(**kwargs)
|
||||
|
||||
* Default widget: ``ClearableFileInput``
|
||||
|
@ -855,11 +833,6 @@ for ``DateField`` are used.
|
|||
If no ``input_time_formats`` argument is provided, the default input formats
|
||||
for ``TimeField`` are used.
|
||||
|
||||
.. versionchanged:: 1.1
|
||||
The ``SplitDateTimeField`` previously used two ``TextInput`` widgets by
|
||||
default. The ``input_date_formats`` and ``input_time_formats`` arguments
|
||||
are also new.
|
||||
|
||||
Fields which handle relationships
|
||||
---------------------------------
|
||||
|
||||
|
|
|
@ -56,8 +56,6 @@ commonly used groups of widgets:
|
|||
|
||||
.. class:: DateInput
|
||||
|
||||
.. versionadded:: 1.1
|
||||
|
||||
Date input as a simple text box: ``<input type='text' ...>``
|
||||
|
||||
Takes one optional argument:
|
||||
|
@ -70,8 +68,6 @@ commonly used groups of widgets:
|
|||
|
||||
.. class:: DateTimeInput
|
||||
|
||||
.. versionadded:: 1.0
|
||||
|
||||
Date/time input as a simple text box: ``<input type='text' ...>``
|
||||
|
||||
Takes one optional argument:
|
||||
|
@ -95,9 +91,6 @@ commonly used groups of widgets:
|
|||
|
||||
If no ``format`` argument is provided, the default format is ``'%H:%M:%S'``.
|
||||
|
||||
.. versionchanged:: 1.1
|
||||
The ``format`` argument was not supported in Django 1.0.
|
||||
|
||||
.. class:: Textarea
|
||||
|
||||
Text area: ``<textarea>...</textarea>``
|
||||
|
@ -167,9 +160,6 @@ commonly used groups of widgets:
|
|||
Takes two optional arguments, ``date_format`` and ``time_format``, which
|
||||
work just like the ``format`` argument for ``DateInput`` and ``TimeInput``.
|
||||
|
||||
.. versionchanged:: 1.1
|
||||
The ``date_format`` and ``time_format`` arguments were not supported in Django 1.0.
|
||||
|
||||
.. class:: SelectDateWidget
|
||||
|
||||
Wrapper around three select widgets: one each for month, day, and year.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue