From e27e4c03399f610e0db1fb9b881095d762fda2b7 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 2 Jan 2017 10:25:57 -0500 Subject: Removed versionadded/changed annotations for 1.10. --- docs/topics/forms/media.txt | 4 ---- docs/topics/forms/modelforms.txt | 10 ---------- 2 files changed, 14 deletions(-) (limited to 'docs/topics/forms') diff --git a/docs/topics/forms/media.txt b/docs/topics/forms/media.txt index adbd2c377e..0bdf237a21 100644 --- a/docs/topics/forms/media.txt +++ b/docs/topics/forms/media.txt @@ -249,10 +249,6 @@ Or if :mod:`~django.contrib.staticfiles` is configured using the -.. versionchanged:: 1.10 - - Older versions didn't serve assets using :mod:`django.contrib.staticfiles`. - ``Media`` objects ================= diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index eb397a3d4a..b0115cef7e 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -342,16 +342,6 @@ there is one, for that field. This behavior doesn't apply to fields that use form submission. Use a custom form field or widget if you're designing an API and want the default fallback for a :class:`~django.db.models.BooleanField`. -.. versionchanged:: 1.10.1 - - Older versions don't have the exception for - :class:`~django.forms.CheckboxInput` which means that unchecked checkboxes - receive a value of ``True`` if that's the model field default. - -.. versionchanged:: 1.10.2 - - The :meth:`~django.forms.Widget.value_omitted_from_data` method was added. - This ``save()`` method accepts an optional ``commit`` keyword argument, which accepts either ``True`` or ``False``. If you call ``save()`` with ``commit=False``, then it will return an object that hasn't yet been saved to -- cgit v1.3