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

A couple more semicolon -> colon fixes; refs #18134.

This commit is contained in:
Tim Graham 2013-07-02 14:14:56 -04:00
parent ddf9ced5bc
commit 3632d289de
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/forms/api.txt
View File

@ -661,7 +661,7 @@ additional attributes for the ``<label>`` tag.
.. versionchanged:: 1.6 .. versionchanged:: 1.6
The label now includes the form's :attr:`~django.forms.Form.label_suffix` The label now includes the form's :attr:`~django.forms.Form.label_suffix`
(a semicolon, by default). (a colon, by default).
.. method:: BoundField.css_classes() .. method:: BoundField.css_classes()

8
docs/releases/1.6.txt
View File

@ -337,8 +337,8 @@ Minor features
default) to allow customizing the :attr:`~django.forms.Form.prefix` of the default) to allow customizing the :attr:`~django.forms.Form.prefix` of the
form. form.
* Raw queries (``Manager.raw()`` or ``cursor.execute()``) can now use the * Raw queries (``Manager.raw()`` or ``cursor.execute()``) can now use the
"pyformat" parameter style, where placeholders in the query are given as "pyformat" parameter style, where placeholders in the query are given as
``'%(name)s'`` and the parameters are passed as a dictionary rather than ``'%(name)s'`` and the parameters are passed as a dictionary rather than
a list (except on SQLite). This has long been possible (but not officially a list (except on SQLite). This has long been possible (but not officially
supported) on MySQL and PostgreSQL, and is now also available on Oracle. supported) on MySQL and PostgreSQL, and is now also available on Oracle.
@ -634,10 +634,10 @@ If you manually render ``label_tag`` in your templates:
{{ form.my_field.label_tag }}: {{ form.my_field }} {{ form.my_field.label_tag }}: {{ form.my_field }}
you'll want to remove the semicolon (or whatever other separator you may be you'll want to remove the colon (or whatever other separator you may be
using) to avoid duplicating it when upgrading to Django 1.6. The following using) to avoid duplicating it when upgrading to Django 1.6. The following
template in Django 1.6 will render identically to the above template in Django template in Django 1.6 will render identically to the above template in Django
1.5, except that the semicolon will appear inside the ``<label>`` element. 1.5, except that the colon will appear inside the ``<label>`` element.
.. code-block:: html+django .. code-block:: html+django