Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Removed versionadded/changed annotations for 1.5

  • Loading branch information...
commit 7b69c3e7758770dd632e1754c30714e91868e037 1 parent 58c6d02
Tim Graham authored

Showing 45 changed files with 65 additions and 400 deletions. Show diff stats Hide diff stats

  1. 6  docs/ref/class-based-views/base.txt
  2. 8  docs/ref/class-based-views/generic-date-based.txt
  3. 5  docs/ref/class-based-views/mixins-date-based.txt
  4. 2  docs/ref/class-based-views/mixins-multiple-object.txt
  5. 4  docs/ref/class-based-views/mixins-simple.txt
  6. 8  docs/ref/contrib/admin/index.txt
  7. 2  docs/ref/contrib/auth.txt
  8. 23  docs/ref/contrib/contenttypes.txt
  9. 4  docs/ref/contrib/gis/geoquerysets.txt
  10. 12  docs/ref/contrib/gis/geos.txt
  11. 4  docs/ref/contrib/staticfiles.txt
  12. 4  docs/ref/databases.txt
  13. 12  docs/ref/django-admin.txt
  14. 4  docs/ref/files/file.txt
  15. 5  docs/ref/forms/api.txt
  16. 9  docs/ref/forms/fields.txt
  17. 10  docs/ref/forms/validation.txt
  18. 5  docs/ref/forms/widgets.txt
  19. 11  docs/ref/models/fields.txt
  20. 2  docs/ref/models/instances.txt
  21. 2  docs/ref/models/options.txt
  22. 38  docs/ref/models/querysets.txt
  23. 8  docs/ref/request-response.txt
  24. 26  docs/ref/settings.txt
  25. 13  docs/ref/signals.txt
  26. 23  docs/ref/template-response.txt
  27. 5  docs/ref/templates/api.txt
  28. 14  docs/ref/templates/builtins.txt
  29. 30  docs/ref/unicode.txt
  30. 14  docs/ref/utils.txt
  31. 2  docs/topics/auth/customizing.txt
  32. 14  docs/topics/auth/default.txt
  33. 2  docs/topics/class-based-views/mixins.txt
  34. 5  docs/topics/db/multi-db.txt
  35. 11  docs/topics/db/queries.txt
  36. 5  docs/topics/http/middleware.txt
  37. 10  docs/topics/http/sessions.txt
  38. 9  docs/topics/http/shortcuts.txt
  39. 2  docs/topics/i18n/translation.txt
  40. 7  docs/topics/logging.txt
  41. 14  docs/topics/pagination.txt
  42. 11  docs/topics/serialization.txt
  43. 4  docs/topics/signals.txt
  44. 2  docs/topics/testing/advanced.txt
  45. 54  docs/topics/testing/overview.txt
6  docs/ref/class-based-views/base.txt
@@ -104,12 +104,6 @@ TemplateView
104 104
     Renders a given template, with the context containing parameters captured
105 105
     in the URL.
106 106
 
107  
-    .. versionchanged:: 1.5
108  
-
109  
-        The context used to be populated with a ``{{ params }}`` dictionary of
110  
-        the parameters captured in the URL. Now those parameters are first-level
111  
-        context variables.
112  
-
113 107
     **Ancestors (MRO)**
114 108
 
115 109
     This view inherits methods and attributes from the following views:
8  docs/ref/class-based-views/generic-date-based.txt
@@ -138,24 +138,16 @@ YearArchiveView
138 138
     * ``year``: A :class:`~datetime.date` object
139 139
       representing the given year.
140 140
 
141  
-      .. versionchanged:: 1.5
142  
-
143  
-         Previously, this returned a string.
144  
-
145 141
     * ``next_year``: A :class:`~datetime.date` object
146 142
       representing the first day of the next year, according to
147 143
       :attr:`~BaseDateListView.allow_empty` and
148 144
       :attr:`~DateMixin.allow_future`.
149 145
 
150  
-      .. versionadded:: 1.5
151  
-
152 146
     * ``previous_year``: A :class:`~datetime.date` object
153 147
       representing the first day of the previous year, according to
154 148
       :attr:`~BaseDateListView.allow_empty` and
155 149
       :attr:`~DateMixin.allow_future`.
156 150
 
157  
-      .. versionadded:: 1.5
158  
-
159 151
     **Notes**
160 152
 
161 153
     * Uses a default ``template_name_suffix`` of ``_archive_year``.
5  docs/ref/class-based-views/mixins-date-based.txt
@@ -328,8 +328,3 @@ BaseDateListView
328 328
         :meth:`~BaseDateListView.get_date_list_period` is used. ``date_type``
329 329
         and ``ordering`` are simply passed to
330 330
         :meth:`QuerySet.dates()<django.db.models.query.QuerySet.dates>`.
331  
-
332  
-        .. versionchanged:: 1.5
333  
-
334  
-            The ``ordering`` parameter was added, and the default order was
335  
-            changed to ascending.
2  docs/ref/class-based-views/mixins-multiple-object.txt
@@ -90,8 +90,6 @@ MultipleObjectMixin
90 90
 
91 91
     .. attribute:: page_kwarg
92 92
 
93  
-        .. versionadded:: 1.5
94  
-
95 93
         A string specifying the name to use for the page parameter.
96 94
         The view will expect this prameter to be available either as a query
97 95
         string parameter (via ``request.GET``) or as a kwarg variable specified
4  docs/ref/class-based-views/mixins-simple.txt
@@ -7,8 +7,6 @@ ContextMixin
7 7
 
8 8
 .. class:: django.views.generic.base.ContextMixin
9 9
 
10  
-    .. versionadded:: 1.5
11  
-
12 10
     **Methods**
13 11
 
14 12
     .. method:: get_context_data(**kwargs)
@@ -77,8 +75,6 @@ TemplateResponseMixin
77 75
 
78 76
     .. attribute:: content_type
79 77
 
80  
-        .. versionadded:: 1.5
81  
-
82 78
         The content type to use for the response. ``content_type`` is passed
83 79
         as a keyword argument to ``response_class``. Default is ``None`` --
84 80
         meaning that Django uses :setting:`DEFAULT_CONTENT_TYPE`.
8  docs/ref/contrib/admin/index.txt
@@ -1235,8 +1235,6 @@ templates used by the :class:`ModelAdmin` views:
1235 1235
 
1236 1236
 .. method:: ModelAdmin.get_list_filter(self, request)
1237 1237
 
1238  
-    .. versionadded:: 1.5
1239  
-
1240 1238
     The ``get_list_filter`` method is given the ``HttpRequest`` and is expected
1241 1239
     to return the same kind of sequence type as for the
1242 1240
     :attr:`~ModelAdmin.list_filter` attribute.
@@ -1251,8 +1249,6 @@ templates used by the :class:`ModelAdmin` views:
1251 1249
 
1252 1250
 .. method:: ModelAdmin.get_inline_instances(self, request, obj=None)
1253 1251
 
1254  
-    .. versionadded:: 1.5
1255  
-
1256 1252
     The ``get_inline_instances`` method is given the ``HttpRequest`` and the
1257 1253
     ``obj`` being edited (or ``None`` on an add form) and is expected to return
1258 1254
     a ``list`` or ``tuple`` of :class:`~django.contrib.admin.InlineModelAdmin`
@@ -1506,10 +1502,6 @@ templates used by the :class:`ModelAdmin` views:
1506 1502
     Sends a message to the user using the :mod:`django.contrib.messages`
1507 1503
     backend.  See the :ref:`custom ModelAdmin example <custom-admin-action>`.
1508 1504
 
1509  
-    .. versionchanged:: 1.5
1510  
-
1511  
-        Keyword arguments were added in Django 1.5.
1512  
-
1513 1505
     Keyword arguments allow you to change the message level, add extra CSS
1514 1506
     tags, or fail silently if the ``contrib.messages`` framework is not
1515 1507
     installed. These keyword arguments match those for
2  docs/ref/contrib/auth.txt
@@ -389,8 +389,6 @@ can be used for notification when a user logs in or out.
389 389
 
390 390
 .. function:: user_login_failed
391 391
 
392  
-    .. versionadded:: 1.5
393  
-
394 392
     Sent when the user failed to login successfully
395 393
 
396 394
     ``sender``
23  docs/ref/contrib/contenttypes.txt
@@ -199,14 +199,18 @@ The ``ContentTypeManager``
199 199
 
200 200
         Takes either a model class or an instance of a model, and returns the
201 201
         :class:`~django.contrib.contenttypes.models.ContentType` instance
202  
-        representing that model.
  202
+        representing that model. ``for_concrete_model=False`` allows fetching
  203
+        the :class:`~django.contrib.contenttypes.models.ContentType` of a proxy
  204
+        model.
203 205
 
204 206
     .. method:: get_for_models(*models[, for_concrete_models=True])
205 207
 
206 208
         Takes a variadic number of model classes, and returns a dictionary
207 209
         mapping the model classes to the
208 210
         :class:`~django.contrib.contenttypes.models.ContentType` instances
209  
-        representing them.
  211
+        representing them. ``for_concrete_models=False`` allows fetching the
  212
+        :class:`~django.contrib.contenttypes.models.ContentType` of proxy
  213
+        models.
210 214
 
211 215
     .. method:: get_by_natural_key(app_label, model)
212 216
 
@@ -232,21 +236,6 @@ lookup::
232 236
 
233 237
 .. _generic-relations:
234 238
 
235  
-.. versionadded:: 1.5
236  
-
237  
-    Prior to Django 1.5,
238  
-    :meth:`~django.contrib.contenttypes.models.ContentTypeManager.get_for_model` and
239  
-    :meth:`~django.contrib.contenttypes.models.ContentTypeManager.get_for_models`
240  
-    always returned the :class:`~django.contrib.contenttypes.models.ContentType`
241  
-    associated with the concrete model of the specified one(s). That means there
242  
-    was no way to retrieve the
243  
-    :class:`~django.contrib.contenttypes.models.ContentType` of a proxy model
244  
-    using those methods. As of Django 1.5 you can now pass a boolean flag –
245  
-    ``for_concrete_model`` and ``for_concrete_models`` respectively – to specify
246  
-    wether or not you want to retrieve the
247  
-    :class:`~django.contrib.contenttypes.models.ContentType` for the concrete or
248  
-    direct model.
249  
-
250 239
 Generic relations
251 240
 =================
252 241
 
4  docs/ref/contrib/gis/geoquerysets.txt
@@ -949,10 +949,6 @@ __ http://geohash.org/
949 949
 
950 950
 *Availability*: PostGIS, SpatiaLite
951 951
 
952  
-.. versionchanged:: 1.5
953  
-
954  
-    ``geojson`` support for Spatialite > 3.0 has been added.
955  
-
956 952
 Attaches a ``geojson`` attribute to every model in the queryset that contains the
957 953
 `GeoJSON`__ representation of the geometry.
958 954
 
12  docs/ref/contrib/gis/geos.txt
@@ -276,10 +276,6 @@ that the SRID value is not included in this representation
276 276
 because it is not a part of the OGC specification (use the
277 277
 :attr:`GEOSGeometry.hexewkb` property instead).
278 278
 
279  
-.. versionchanged:: 1.5
280  
-
281  
-    Prior to Django 1.5, the Z value of the geometry was dropped.
282  
-
283 279
 .. attribute:: GEOSGeometry.hexewkb
284 280
 
285 281
 Returns the EWKB of this Geometry in hexadecimal form.  This is an
@@ -325,10 +321,6 @@ Returns the WKB (Well-Known Binary) representation of this Geometry
325 321
 as a Python buffer.  SRID value is not included, use the
326 322
 :attr:`GEOSGeometry.ewkb` property instead.
327 323
 
328  
-.. versionchanged:: 1.5
329  
-
330  
-    Prior to Django 1.5, the Z value of the geometry was dropped.
331  
-
332 324
 .. _ewkb:
333 325
 
334 326
 .. attribute:: GEOSGeometry.ewkb
@@ -426,8 +418,6 @@ geometry that do not make up other.
426 418
 .. method:: GEOSGeometry.interpolate(distance)
427 419
 .. method:: GEOSGeometry.interpolate_normalized(distance)
428 420
 
429  
-.. versionadded:: 1.5
430  
-
431 421
 Given a distance (float), returns the point (or closest point) within the
432 422
 geometry (:class:`LineString` or :class:`MultiLineString`) at that distance.
433 423
 The normalized version takes the distance as a float between 0 (origin) and 1
@@ -443,8 +433,6 @@ geometry and other.
443 433
 .. method:: GEOSGeometry.project(point)
444 434
 .. method:: GEOSGeometry.project_normalized(point)
445 435
 
446  
-.. versionadded:: 1.5
447  
-
448 436
 Returns the distance (float) from the origin of the geometry
449 437
 (:class:`LineString` or :class:`MultiLineString`) to the point projected on the
450 438
 geometry (that is to a point of the line the closest to the given point).
4  docs/ref/contrib/staticfiles.txt
@@ -255,8 +255,6 @@ CachedStaticFilesStorage
255 255
 
256 256
     .. method:: file_hash(name, content=None)
257 257
 
258  
-    .. versionadded:: 1.5
259  
-
260 258
     The method that is used when creating the hashed name of a file.
261 259
     Needs to return a hash for the given file name and content.
262 260
     By default it calculates a MD5 hash from the content's chunks as
@@ -290,8 +288,6 @@ The previous example is equal to calling the ``url`` method of an instance of
290 288
 useful when using a non-local storage backend to deploy files as documented
291 289
 in :ref:`staticfiles-from-cdn`.
292 290
 
293  
-.. versionadded:: 1.5
294  
-
295 291
 If you'd like to retrieve a static URL without displaying it, you can use a
296 292
 slightly different call:
297 293
 
4  docs/ref/databases.txt
@@ -191,10 +191,6 @@ Django supports MySQL 5.0.3 and higher.
191 191
 `MySQL 5.0`_ adds the ``information_schema`` database, which contains detailed
192 192
 data on all database schema. Django's ``inspectdb`` feature uses it.
193 193
 
194  
-.. versionchanged:: 1.5
195  
-
196  
-    The minimum version requirement of MySQL 5.0.3 was set in Django 1.5.
197  
-
198 194
 Django expects the database to support Unicode (UTF-8 encoding) and delegates to
199 195
 it the task of enforcing transactions and referential integrity. It is important
200 196
 to be aware of the fact that the two latter ones aren't actually enforced by
12  docs/ref/django-admin.txt
@@ -256,8 +256,6 @@ to flush.
256 256
 ``--no-initial-data``
257 257
 ~~~~~~~~~~~~~~~~~~~~~
258 258
 
259  
-.. versionadded:: 1.5
260  
-
261 259
 Use ``--no-initial-data`` to avoid loading the initial_data fixture.
262 260
 
263 261
 
@@ -334,8 +332,6 @@ onto which the data will be loaded.
334 332
 
335 333
 .. django-admin-option:: --ignorenonexistent
336 334
 
337  
-.. versionadded:: 1.5
338  
-
339 335
 The :djadminopt:`--ignorenonexistent` option can be used to ignore fields that
340 336
 may have been removed from models since the fixture was originally generated.
341 337
 
@@ -859,10 +855,6 @@ behavior you can use the ``--no-startup`` option. e.g.::
859 855
 
860 856
     django-admin.py shell --plain --no-startup
861 857
 
862  
-.. versionadded:: 1.5
863  
-
864  
-    The ``--interface`` option was added in Django 1.5.
865  
-
866 858
 .. versionadded:: 1.6
867 859
 
868 860
     The ``--no-startup`` option was added in Django 1.6.
@@ -1148,8 +1140,6 @@ synchronize.
1148 1140
 ``--no-initial-data``
1149 1141
 ~~~~~~~~~~~~~~~~~~~~~
1150 1142
 
1151  
-.. versionadded:: 1.5
1152  
-
1153 1143
 Use ``--no-initial-data`` to avoid loading the initial_data fixture.
1154 1144
 
1155 1145
 test <app or test identifier>
@@ -1327,8 +1317,6 @@ clearsessions
1327 1317
 
1328 1318
 .. django-admin:: clearsessions
1329 1319
 
1330  
-.. versionadded:: 1.5
1331  
-
1332 1320
 Can be run as a cron job or directly to clean out expired sessions.
1333 1321
 
1334 1322
 ``django.contrib.sitemaps``
4  docs/ref/files/file.txt
@@ -100,10 +100,6 @@ The ``ContentFile`` Class
100 100
         f1 = ContentFile("esta sentencia está en español")
101 101
         f2 = ContentFile(b"these are bytes")
102 102
 
103  
-    .. versionchanged:: 1.5
104  
-
105  
-        ContentFile also accepts Unicode strings.
106  
-
107 103
 .. currentmodule:: django.core.files.images
108 104
 
109 105
 The ``ImageFile`` Class
5  docs/ref/forms/api.txt
@@ -211,11 +211,6 @@ only the valid fields::
211 211
     >>> f.cleaned_data
212 212
     {'cc_myself': True, 'message': u'Hi there'}
213 213
 
214  
-.. versionchanged:: 1.5
215  
-
216  
-Until Django 1.5, the ``cleaned_data`` attribute wasn't defined at all when
217  
-the ``Form`` didn't validate.
218  
-
219 214
 ``cleaned_data`` will always *only* contain a key for fields defined in the
220 215
 ``Form``, even if you pass extra data when you define the ``Form``. In this
221 216
 example, we pass a bunch of extra fields to the ``ContactForm`` constructor,
9  docs/ref/forms/fields.txt
@@ -573,16 +573,12 @@ For each field, we describe the default widget used if you don't specify
573 573
 
574 574
     .. attribute:: allow_files
575 575
 
576  
-        .. versionadded:: 1.5
577  
-
578 576
         Optional.  Either ``True`` or ``False``.  Default is ``True``.  Specifies
579 577
         whether files in the specified location should be included.  Either this or
580 578
         :attr:`allow_folders` must be ``True``.
581 579
 
582 580
     .. attribute:: allow_folders
583 581
 
584  
-        .. versionadded:: 1.5
585  
-
586 582
         Optional.  Either ``True`` or ``False``.  Default is ``False``.  Specifies
587 583
         whether folders in the specified location should be included.  Either this or
588 584
         :attr:`allow_files` must be ``True``.
@@ -1065,11 +1061,6 @@ objects (in the case of ``ModelMultipleChoiceField``) into the
1065 1061
     * Error message keys: ``required``, ``list``, ``invalid_choice``,
1066 1062
       ``invalid_pk_value``
1067 1063
 
1068  
-    .. versionchanged:: 1.5
1069  
-
1070  
-        The empty and normalized values were changed to be consistently
1071  
-        ``QuerySets`` instead of ``[]`` and ``QuerySet`` respectively.
1072  
-
1073 1064
     .. versionchanged:: 1.6
1074 1065
 
1075 1066
         The ``invalid_choice`` message may contain ``%(value)s`` and the
10  docs/ref/forms/validation.txt
@@ -450,11 +450,5 @@ entries in ``_errors``.
450 450
 
451 451
 Secondly, once we have decided that the combined data in the two fields we are
452 452
 considering aren't valid, we must remember to remove them from the
453  
-``cleaned_data``.
454  
-
455  
-.. versionchanged:: 1.5
456  
-
457  
-    Django used to remove the ``cleaned_data`` attribute entirely if there were
458  
-    any errors in the form. Since version 1.5, ``cleaned_data`` is present even if
459  
-    the form doesn't validate, but it contains only field values that did
460  
-    validate.
  453
+``cleaned_data``. `cleaned_data`` is present even if the form doesn't
  454
+validate, but it contains only field values that did validate.
5  docs/ref/forms/widgets.txt
@@ -525,11 +525,6 @@ Selector and checkbox widgets
525 525
         A callable that takes the value of the CheckBoxInput and returns
526 526
         ``True`` if the checkbox should be checked for that value.
527 527
 
528  
-        .. versionchanged:: 1.5
529  
-
530  
-            Exceptions from ``check_test`` used to be silenced by its caller,
531  
-            this is no longer the case, they will propagate upwards.
532  
-
533 528
 ``Select``
534 529
 ~~~~~~~~~~
535 530
 
11  docs/ref/models/fields.txt
@@ -757,21 +757,16 @@ directory on the filesystem. Has three special arguments, of which the first is
757 757
 
758 758
 .. attribute:: FilePathField.allow_files
759 759
 
760  
-    .. versionadded:: 1.5
761  
-
762 760
     Optional.  Either ``True`` or ``False``.  Default is ``True``.  Specifies
763 761
     whether files in the specified location should be included.  Either this or
764 762
     :attr:`~FilePathField.allow_folders` must be ``True``.
765 763
 
766 764
 .. attribute:: FilePathField.allow_folders
767 765
 
768  
-    .. versionadded:: 1.5
769  
-
770 766
     Optional.  Either ``True`` or ``False``.  Default is ``False``.  Specifies
771 767
     whether folders in the specified location should be included.  Either this
772 768
     or :attr:`~FilePathField.allow_files` must be ``True``.
773 769
 
774  
-
775 770
 Of course, these arguments can be used together.
776 771
 
777 772
 The one potential gotcha is that :attr:`~FilePathField.match` applies to the
@@ -980,12 +975,6 @@ Like all :class:`CharField` subclasses, :class:`URLField` takes the optional
980 975
 :attr:`~CharField.max_length` argument. If you don't specify
981 976
 :attr:`~CharField.max_length`, a default of 200 is used.
982 977
 
983  
-.. versionadded:: 1.5
984  
-
985  
-    The current value of the field will be displayed as a clickable link above the
986  
-    input widget.
987  
-
988  
-
989 978
 Relationship fields
990 979
 ===================
991 980
 
2  docs/ref/models/instances.txt
@@ -388,8 +388,6 @@ For more details, see the documentation on :ref:`F() expressions
388 388
 Specifying which fields to save
389 389
 -------------------------------
390 390
 
391  
-.. versionadded:: 1.5
392  
-
393 391
 If ``save()`` is passed a list of field names in keyword argument
394 392
 ``update_fields``, only the fields named in that list will be updated.
395 393
 This may be desirable if you want to update just one or a few fields on
2  docs/ref/models/options.txt
@@ -286,8 +286,6 @@ Django quotes column and table names behind the scenes.
286 286
 
287 287
 .. attribute:: Options.index_together
288 288
 
289  
-    .. versionadded:: 1.5
290  
-
291 289
     Sets of field names that, taken together, are indexed::
292 290
 
293 291
         index_together = [
38  docs/ref/models/querysets.txt
@@ -1149,13 +1149,11 @@ to ``defer()``::
1149 1149
     # Load all fields immediately.
1150 1150
     my_queryset.defer(None)
1151 1151
 
1152  
-.. versionchanged:: 1.5
1153  
-
1154  
-    Some fields in a model won't be deferred, even if you ask for them. You can
1155  
-    never defer the loading of the primary key. If you are using
1156  
-    :meth:`select_related()` to retrieve related models, you shouldn't defer the
1157  
-    loading of the field that connects from the primary model to the related
1158  
-    one, doing so will result in an error.
  1152
+Some fields in a model won't be deferred, even if you ask for them. You can
  1153
+never defer the loading of the primary key. If you are using
  1154
+:meth:`select_related()` to retrieve related models, you shouldn't defer the
  1155
+loading of the field that connects from the primary model to the related
  1156
+one, doing so will result in an error.
1159 1157
 
1160 1158
 .. note::
1161 1159
 
@@ -1178,8 +1176,6 @@ to ``defer()``::
1178 1176
     reader, is slightly faster and consumes a little less memory in the Python
1179 1177
     process.
1180 1178
 
1181  
-.. versionchanged:: 1.5
1182  
-
1183 1179
 .. note::
1184 1180
 
1185 1181
     When calling :meth:`~django.db.models.Model.save()` for instances with
@@ -1227,16 +1223,14 @@ All of the cautions in the note for the :meth:`defer` documentation apply to
1227 1223
 ``only()`` as well. Use it cautiously and only after exhausting your other
1228 1224
 options.
1229 1225
 
1230  
-.. versionchanged:: 1.5
1231  
-
1232  
-    Using :meth:`only` and omitting a field requested using
1233  
-    :meth:`select_related` is an error as well.
  1226
+Using :meth:`only` and omitting a field requested using :meth:`select_related`
  1227
+is an error as well.
1234 1228
 
1235  
-    .. note::
  1229
+.. note::
1236 1230
 
1237  
-        When calling :meth:`~django.db.models.Model.save()` for instances with
1238  
-        deferred fields, only the loaded fields will be saved. See
1239  
-        :meth:`~django.db.models.Model.save()` for more details.
  1231
+    When calling :meth:`~django.db.models.Model.save()` for instances with
  1232
+    deferred fields, only the loaded fields will be saved. See
  1233
+    :meth:`~django.db.models.Model.save()` for more details.
1240 1234
 
1241 1235
 using
1242 1236
 ~~~~~
@@ -1567,10 +1561,6 @@ The ``batch_size`` parameter controls how many objects are created in single
1567 1561
 query. The default is to create all objects in one batch, except for SQLite
1568 1562
 where the default is such that at maximum 999 variables per query is used.
1569 1563
 
1570  
-.. versionadded:: 1.5
1571  
-
1572  
-    The ``batch_size`` parameter was added in version 1.5.
1573  
-
1574 1564
 count
1575 1565
 ~~~~~
1576 1566
 
@@ -1900,10 +1890,6 @@ methods on your models. It does, however, emit the
1900 1890
 :data:`~django.db.models.signals.post_delete` signals for all deleted objects
1901 1891
 (including cascaded deletions).
1902 1892
 
1903  
-.. versionadded:: 1.5
1904  
-
1905  
-    Allow fast-path deletion of objects.
1906  
-
1907 1893
 Django needs to fetch objects into memory to send signals and handle cascades.
1908 1894
 However, if there are no cascades and no signals, then Django may take a
1909 1895
 fast-path and delete objects without fetching into memory. For large
@@ -1911,7 +1897,7 @@ deletes this can result in significantly reduced memory usage. The amount of
1911 1897
 executed queries can be reduced, too.
1912 1898
 
1913 1899
 ForeignKeys which are set to :attr:`~django.db.models.ForeignKey.on_delete`
1914  
-DO_NOTHING do not prevent taking the fast-path in deletion.
  1900
+``DO_NOTHING`` do not prevent taking the fast-path in deletion.
1915 1901
 
1916 1902
 Note that the queries generated in object deletion is an implementation
1917 1903
 detail subject to change.
8  docs/ref/request-response.txt
@@ -93,10 +93,6 @@ All attributes should be considered read-only, unless stated otherwise below.
93 93
     non-form data posted in the request, access this through the
94 94
     :attr:`HttpRequest.body` attribute instead.
95 95
 
96  
-    .. versionchanged:: 1.5
97  
-
98  
-        Before Django 1.5, HttpRequest.POST contained non-form data.
99  
-
100 96
     It's possible that a request can come in via POST with an empty ``POST``
101 97
     dictionary -- if, say, a form is requested via the POST HTTP method but
102 98
     does not include form data. Therefore, you shouldn't use ``if request.POST``
@@ -196,8 +192,6 @@ All attributes should be considered read-only, unless stated otherwise below.
196 192
 
197 193
 .. attribute:: HttpRequest.resolver_match
198 194
 
199  
-    .. versionadded:: 1.5
200  
-
201 195
     An instance of :class:`~django.core.urlresolvers.ResolverMatch` representing
202 196
     the resolved url. This attribute is only set after url resolving took place,
203 197
     which means it's available in all views but not in middleware methods which
@@ -824,8 +818,6 @@ types of HTTP responses. Like ``HttpResponse``, these subclasses live in
824 818
 StreamingHttpResponse objects
825 819
 =============================
826 820
 
827  
-.. versionadded:: 1.5
828  
-
829 821
 .. class:: StreamingHttpResponse
830 822
 
831 823
 The :class:`StreamingHttpResponse` class is used to stream a response from
26  docs/ref/settings.txt
@@ -1542,6 +1542,8 @@ unpredictable value.
1542 1542
 :djadmin:`django-admin.py startproject <startproject>` automatically adds a
1543 1543
 randomly-generated ``SECRET_KEY`` to each new project.
1544 1544
 
  1545
+Django will refuse to start if :setting:`SECRET_KEY` is not set.
  1546
+
1545 1547
 .. warning::
1546 1548
 
1547 1549
     **Keep this value secret.**
@@ -1550,10 +1552,6 @@ randomly-generated ``SECRET_KEY`` to each new project.
1550 1552
     security protections, and can lead to privilege escalation and remote code
1551 1553
     execution vulnerabilities.
1552 1554
 
1553  
-.. versionchanged:: 1.5
1554  
-
1555  
-    Django will now refuse to start if :setting:`SECRET_KEY` is not set.
1556  
-
1557 1555
 .. setting:: SECURE_PROXY_SSL_HEADER
1558 1556
 
1559 1557
 SECURE_PROXY_SSL_HEADER
@@ -2108,13 +2106,9 @@ The URL where requests are redirected after login when the
2108 2106
 This is used by the :func:`~django.contrib.auth.decorators.login_required`
2109 2107
 decorator, for example.
2110 2108
 
2111  
-.. versionchanged:: 1.5
2112  
-
2113  
-    This setting now also accepts view function names and
2114  
-    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
2115  
-    configuration duplication since you no longer have to define the URL in two
2116  
-    places (``settings`` and URLconf).
2117  
-    For backward compatibility reasons the default remains unchanged.
  2109
+This setting also accepts view function names and :ref:`named URL patterns
  2110
+<naming-url-patterns>` which can be used to reduce configuration duplication
  2111
+since you don't have to define the URL in two places (``settings`` and URLconf).
2118 2112
 
2119 2113
 .. setting:: LOGIN_URL
2120 2114
 
@@ -2126,13 +2120,9 @@ Default: ``'/accounts/login/'``
2126 2120
 The URL where requests are redirected for login, especially when using the
2127 2121
 :func:`~django.contrib.auth.decorators.login_required` decorator.
2128 2122
 
2129  
-.. versionchanged:: 1.5
2130  
-
2131  
-    This setting now also accepts view function names and
2132  
-    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
2133  
-    configuration duplication since you no longer have to define the URL in two
2134  
-    places (``settings`` and URLconf).
2135  
-    For backward compatibility reasons the default remains unchanged.
  2123
+This setting also accepts view function names and :ref:`named URL patterns
  2124
+<naming-url-patterns>` which can be used to reduce configuration duplication
  2125
+since you don't have to define the URL in two places (``settings`` and URLconf).
2136 2126
 
2137 2127
 .. setting:: LOGOUT_URL
2138 2128
 
13  docs/ref/signals.txt
@@ -118,8 +118,6 @@ Arguments sent with this signal:
118 118
 ``using``
119 119
     The database alias being used.
120 120
 
121  
-.. versionadded:: 1.5
122  
-
123 121
 ``update_fields``
124 122
     The set of fields to update explicitly specified in the ``save()`` method.
125 123
     ``None`` if this argument was not used in the ``save()`` call.
@@ -153,8 +151,6 @@ Arguments sent with this signal:
153 151
 ``using``
154 152
     The database alias being used.
155 153
 
156  
-.. versionadded:: 1.5
157  
-
158 154
 ``update_fields``
159 155
     The set of fields to update explicitly specified in the ``save()`` method.
160 156
     ``None`` if this argument was not used in the ``save()`` call.
@@ -496,14 +492,7 @@ request_finished
496 492
 .. data:: django.core.signals.request_finished
497 493
    :module:
498 494
 
499  
-Sent when Django finishes processing an HTTP request.
500  
-
501  
-.. versionchanged:: 1.5
502  
-
503  
-    Before Django 1.5, this signal was sent before delivering content to the
504  
-    client. In order to accommodate :ref:`streaming responses
505  
-    <httpresponse-streaming>`, it is now sent after the response has been fully
506  
-    delivered to the client.
  495
+Sent when Django finishes delvering an HTTP response to the client.
507 496
 
508 497
 .. note::
509 498
 
23  docs/ref/template-response.txt
@@ -75,16 +75,10 @@ Methods
75 75
         The HTTP Status code for the response.
76 76
 
77 77
     ``content_type``
78  
-
79  
-        .. versionchanged:: 1.5
80  
-
81  
-            Historically, this parameter was only called ``mimetype`` (now
82  
-            deprecated), but since this is actually the value included in the HTTP
83  
-            ``Content-Type`` header, it can also include the character set
84  
-            encoding, which makes it more than just a MIME type specification. If
85  
-            ``content_type`` is specified, then its value is used. Otherwise,
86  
-            :setting:`DEFAULT_CONTENT_TYPE` is used.
87  
-
  78
+        The value included in the HTTP ``Content-Type`` header, including the
  79
+        MIME type specification and the character set encoding. If
  80
+        ``content_type`` is specified, then its value is used. Otherwise,
  81
+        :setting:`DEFAULT_CONTENT_TYPE` is used.
88 82
 
89 83
 .. method:: SimpleTemplateResponse.resolve_context(context)
90 84
 
@@ -167,13 +161,8 @@ Methods
167 161
         The HTTP Status code for the response.
168 162
 
169 163
     ``content_type``
170  
-
171  
-        .. versionchanged:: 1.5
172  
-
173  
-        Historically, this parameter was only called ``mimetype`` (now
174  
-        deprecated), but since this is actually the value included in the HTTP
175  
-        ``Content-Type`` header, it can also include the character set
176  
-        encoding, which makes it more than just a MIME type specification. If
  164
+        The value included in the HTTP ``Content-Type`` header, including the
  165
+        MIME type specification and the character set encoding. If
177 166
         ``content_type`` is specified, then its value is used. Otherwise,
178 167
         :setting:`DEFAULT_CONTENT_TYPE` is used.
179 168
 
5  docs/ref/templates/api.txt
@@ -274,11 +274,6 @@ Builtin variables
274 274
 Every context contains ``True``, ``False`` and ``None``. As you would expect,
275 275
 these variables resolve to the corresponding Python objects.
276 276
 
277  
-.. versionadded:: 1.5
278  
-
279  
-    Before Django 1.5, these variables weren't a special case, and they
280  
-    resolved to ``None`` unless you defined them in the context.
281  
-
282 277
 Playing with Context objects
283 278
 ----------------------------
284 279
 
14  docs/ref/templates/builtins.txt
@@ -1059,22 +1059,14 @@ by the context as to the current application.
1059 1059
 
1060 1060
 .. warning::
1061 1061
 
1062  
-    Don't forget to put quotes around the function path or pattern name!
1063  
-
1064  
-    .. versionchanged:: 1.5
1065  
-
1066  
-        The first parameter used not to be quoted, which was inconsistent with
1067  
-        other template tags. Since Django 1.5, it is evaluated according to
1068  
-        the usual rules: it can be a quoted string or a variable that will be
1069  
-        looked up in the context.
  1062
+    Don't forget to put quotes around the function path or pattern name,
  1063
+    otherwise the value will be interpreted as a context variable!
1070 1064
 
1071 1065
 .. templatetag:: verbatim
1072 1066
 
1073 1067
 verbatim
1074 1068
 ^^^^^^^^
1075 1069
 
1076  
-.. versionadded:: 1.5
1077  
-
1078 1070
 Stops the template engine from rendering the contents of this block tag.
1079 1071
 
1080 1072
 A common use is to allow a Javascript template layer that collides with
@@ -2411,8 +2403,6 @@ It is also able to consume standard context variables, e.g. assuming a
2411 2403
 If you'd like to retrieve a static URL without displaying it, you can use a
2412 2404
 slightly different call:
2413 2405
 
2414  
-.. versionadded:: 1.5
2415  
-
2416 2406
 .. code-block:: html+django
2417 2407
 
2418 2408
     {% load static %}
30  docs/ref/unicode.txt
@@ -45,28 +45,26 @@ rendering or anywhere else -- you have two choices for encoding those strings.
45 45
 You can use Unicode strings, or you can use normal strings (sometimes called
46 46
 "bytestrings") that are encoded using UTF-8.
47 47
 
48  
-.. versionchanged:: 1.5
  48
+In Python 3, the logic is reversed, that is normal strings are Unicode, and
  49
+when you want to specifically create a bytestring, you have to prefix the
  50
+string with a 'b'. As we are doing in Django code from version 1.5,
  51
+we recommend that you import ``unicode_literals`` from the __future__ library
  52
+in your code. Then, when you specifically want to create a bytestring literal,
  53
+prefix the string with 'b'.
49 54
 
50  
-    In Python 3, the logic is reversed, that is normal strings are Unicode, and
51  
-    when you want to specifically create a bytestring, you have to prefix the
52  
-    string with a 'b'. As we are doing in Django code from version 1.5,
53  
-    we recommend that you import ``unicode_literals`` from the __future__ library
54  
-    in your code. Then, when you specifically want to create a bytestring literal,
55  
-    prefix the string with 'b'.
  55
+Python 2 legacy::
56 56
 
57  
-    Python 2 legacy::
  57
+    my_string = "This is a bytestring"
  58
+    my_unicode = u"This is an Unicode string"
58 59
 
59  
-        my_string = "This is a bytestring"
60  
-        my_unicode = u"This is an Unicode string"
  60
+Python 2 with unicode literals or Python 3::
61 61
 
62  
-    Python 2 with unicode literals or Python 3::
63  
-
64  
-        from __future__ import unicode_literals
  62
+    from __future__ import unicode_literals
65 63
 
66  
-        my_string = b"This is a bytestring"
67  
-        my_unicode = "This is an Unicode string"
  64
+    my_string = b"This is a bytestring"
  65
+    my_unicode = "This is an Unicode string"
68 66
 
69  
-    See also :doc:`Python 3 compatibility </topics/python3>`.
  67
+See also :doc:`Python 3 compatibility </topics/python3>`.
70 68
 
71 69
 .. warning::
72 70
 
14  docs/ref/utils.txt
@@ -204,8 +204,6 @@ The functions defined in this module share the following properties:
204 204
 
205 205
 .. function:: smart_text(s, encoding='utf-8', strings_only=False, errors='strict')
206 206
 
207  
-    .. versionadded:: 1.5
208  
-
209 207
     Returns a text object representing ``s`` -- ``unicode`` on Python 2 and
210 208
     ``str`` on Python 3. Treats bytestrings using the ``encoding`` codec.
211 209
 
@@ -225,8 +223,6 @@ The functions defined in this module share the following properties:
225 223
 
226 224
 .. function:: force_text(s, encoding='utf-8', strings_only=False, errors='strict')
227 225
 
228  
-    .. versionadded:: 1.5
229  
-
230 226
     Similar to ``smart_text``, except that lazy instances are resolved to
231 227
     strings, rather than kept as lazy objects.
232 228
 
@@ -239,8 +235,6 @@ The functions defined in this module share the following properties:
239 235
 
240 236
 .. function:: smart_bytes(s, encoding='utf-8', strings_only=False, errors='strict')
241 237
 
242  
-    .. versionadded:: 1.5
243  
-
244 238
     Returns a bytestring version of ``s``, encoded as specified in
245 239
     ``encoding``.
246 240
 
@@ -249,8 +243,6 @@ The functions defined in this module share the following properties:
249 243
 
250 244
 .. function:: force_bytes(s, encoding='utf-8', strings_only=False, errors='strict')
251 245
 
252  
-    .. versionadded:: 1.5
253  
-
254 246
     Similar to ``smart_bytes``, except that lazy instances are resolved to
255 247
     bytestrings, rather than kept as lazy objects.
256 248
 
@@ -745,8 +737,6 @@ appropriate entities.
745 737
 
746 738
 .. class:: SafeBytes
747 739
 
748  
-    .. versionadded:: 1.5
749  
-
750 740
     A ``bytes`` subclass that has been specifically marked as "safe"
751 741
     (requires no further escaping) for HTML output purposes.
752 742
 
@@ -758,8 +748,6 @@ appropriate entities.
758 748
 
759 749
 .. class:: SafeText
760 750
 
761  
-    .. versionadded:: 1.5
762  
-
763 751
     A ``str`` (in Python 3) or ``unicode`` (in Python 2) subclass
764 752
     that has been specifically marked as "safe" for HTML output purposes.
765 753
 
@@ -977,8 +965,6 @@ For a complete discussion on the usage of the following see the
977 965
     ``None``, the :ref:`current time zone <default-current-time-zone>` is unset
978 966
     on entry with :func:`deactivate()` instead.
979 967
 
980  
-.. versionadded:: 1.5
981  
-
982 968
 .. function:: localtime(value, timezone=None)
983 969
 
984 970
     Converts an aware :class:`~datetime.datetime` to a different time zone,
2  docs/topics/auth/customizing.txt
@@ -359,8 +359,6 @@ the extra database load.
359 359
 Substituting a custom User model
360 360
 ================================
361 361
 
362  
-.. versionadded:: 1.5
363  
-
364 362
 Some kinds of projects may have authentication requirements for which Django's
365 363
 built-in :class:`~django.contrib.auth.models.User` model is not always
366 364
 appropriate. For instance, on some sites it makes more sense to use an email
14  docs/topics/auth/default.txt
@@ -434,12 +434,10 @@ The login_required decorator
434 434
 
435 435
         (r'^accounts/login/$', 'django.contrib.auth.views.login'),
436 436
 
437  
-    .. versionchanged:: 1.5
438  
-
439  
-        The :setting:`settings.LOGIN_URL <LOGIN_URL>` also accepts
440  
-        view function names and :ref:`named URL patterns <naming-url-patterns>`.
441  
-        This allows you to freely remap your login view within your URLconf
442  
-        without having to update the setting.
  437
+    The :setting:`settings.LOGIN_URL <LOGIN_URL>` also accepts view function
  438
+    names and :ref:`named URL patterns <naming-url-patterns>`. This allows you
  439
+    to freely remap your login view within your URLconf without having to
  440
+    update the setting.
443 441
 
444 442
 .. note::
445 443
 
@@ -1187,10 +1185,6 @@ Thus, you can check permissions in template ``{% if %}`` statements:
1187 1185
         <p>You don't have permission to do anything in the foo app.</p>
1188 1186
     {% endif %}
1189 1187
 
1190  
-.. versionadded:: 1.5
1191  
-
1192  
-    Permission lookup by "if in".
1193  
-
1194 1188
 It is possible to also look permissions up by ``{% if in %}`` statements.
1195 1189
 For example:
1196 1190
 
2  docs/topics/class-based-views/mixins.txt
@@ -55,8 +55,6 @@ interface to working with templates in class-based views.
55 55
     override this to provide more flexible defaults when dealing with actual
56 56
     objects.
57 57
 
58  
-.. versionadded:: 1.5
59  
-
60 58
 :class:`~django.views.generic.base.ContextMixin`
61 59
     Every built in view which needs context data, such as for rendering a
62 60
     template (including ``TemplateResponseMixin`` above), should call
5  docs/topics/db/multi-db.txt
@@ -680,11 +680,6 @@ In addition, some objects are automatically created just after
680 680
 - three ``Permission`` for each model (including those not stored in that
681 681
   database).
682 682
 
683  
-.. versionchanged:: 1.5
684  
-
685  
-    Previously, ``ContentType`` and ``Permission`` instances were created only
686  
-    in the default database.
687  
-
688 683
 For common setups with multiple databases, it isn't useful to have these
689 684
 objects in more than one database. Common setups include master / slave and
690 685
 connecting to external databases. Therefore, it's recommended:
11  docs/topics/db/queries.txt
@@ -639,20 +639,11 @@ that were modified more than 3 days after they were published::
639 639
     >>> from datetime import timedelta
640 640
     >>> Entry.objects.filter(mod_date__gt=F('pub_date') + timedelta(days=3))
641 641
 
642  
-.. versionadded:: 1.5
643  
-
644  
-    ``.bitand()`` and ``.bitor()``
645  
-
646  
-The ``F()`` objects now support bitwise operations by ``.bitand()`` and
  642
+The ``F()`` objects support bitwise operations by ``.bitand()`` and
647 643
 ``.bitor()``, for example::
648 644
 
649 645
     >>> F('somefield').bitand(16)
650 646
 
651  
-.. versionchanged:: 1.5
652  
-
653  
-    The previously undocumented operators ``&`` and ``|`` no longer produce
654  
-    bitwise operations, use ``.bitand()`` and ``.bitor()`` instead.
655  
-
656 647
 The pk lookup shortcut
657 648
 ----------------------
658 649
 
5  docs/topics/http/middleware.txt
@@ -204,11 +204,6 @@ reverse order, from the bottom up. This means classes defined at the end of
204 204
 Dealing with streaming responses
205 205
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
206 206
 
207  
-.. versionchanged:: 1.5
208  
-
209  
-    ``response`` may also be an :class:`~django.http.StreamingHttpResponse`
210  
-    object.
211  
-
212 207
 Unlike :class:`~django.http.HttpResponse`,
213 208
 :class:`~django.http.StreamingHttpResponse` does not have a ``content``
214 209
 attribute. As a result, middleware can no longer assume that all responses
10  docs/topics/http/sessions.txt
@@ -70,10 +70,6 @@ If you have multiple caches defined in :setting:`CACHES`, Django will use the
70 70
 default cache. To use another cache, set :setting:`SESSION_CACHE_ALIAS` to the
71 71
 name of that cache.
72 72
 
73  
-.. versionchanged:: 1.5
74  
-
75  
-    The :setting:`SESSION_CACHE_ALIAS` setting was added.
76  
-
77 73
 Once your cache is configured, you've got two choices for how to store data in
78 74
 the cache:
79 75
 
@@ -302,8 +298,6 @@ You can edit it multiple times.
302 298
 
303 299
     .. method:: SessionBase.clear_expired
304 300
 
305  
-      .. versionadded:: 1.5
306  
-
307 301
       Removes expired sessions from the session store. This class method is
308 302
       called by :djadmin:`clearsessions`.
309 303
 
@@ -469,9 +463,7 @@ cookie will be sent on every request.
469 463
 Similarly, the ``expires`` part of a session cookie is updated each time the
470 464
 session cookie is sent.
471 465
 
472  
-.. versionchanged:: 1.5
473  
-
474  
-  The session is not saved if the response's status code is 500.
  466
+The session is not saved if the response's status code is 500.
475 467
 
476 468
 .. _browser-length-vs-persistent-sessions:
477 469
 
9  docs/topics/http/shortcuts.txt
@@ -50,10 +50,6 @@ Optional arguments
50 50
     The MIME type to use for the resulting document. Defaults to the value of
51 51
     the :setting:`DEFAULT_CONTENT_TYPE` setting.
52 52
 
53  
-    .. versionchanged:: 1.5
54  
-
55  
-        This parameter used to be called ``mimetype``.
56  
-
57 53
 ``status``
58 54
     The status code for the response. Defaults to ``200``.
59 55
 
@@ -129,11 +125,6 @@ Optional arguments
129 125
     The MIME type to use for the resulting document. Defaults to the value of
130 126
     the :setting:`DEFAULT_CONTENT_TYPE` setting.
131 127
 
132  
-    .. versionchanged:: 1.5
133  
-
134  
-        This parameter used to be called ``mimetype``.
135  
-
136  
-
137 128
 Example
138 129
 -------
139 130
 
2  docs/topics/i18n/translation.txt
@@ -1031,8 +1031,6 @@ in django-statici18n_.
1031 1031
 Internationalization: in URL patterns
1032 1032
 =====================================
1033 1033
 
1034  
-..  versionadded:: 1.4
1035  
-
1036 1034
 .. module:: django.conf.urls.i18n
1037 1035
 
1038 1036
 Django provides two mechanisms to internationalize URL patterns:
7  docs/topics/logging.txt
@@ -581,8 +581,6 @@ logging module.
581 581
 
582 582
 .. class:: RequireDebugTrue()
583 583
 
584  
-   .. versionadded:: 1.5
585  
-
586 584
    This filter is similar to :class:`RequireDebugFalse`, except that records are
587 585
    passed only when :setting:`DEBUG` is ``True``.
588 586
 
@@ -599,10 +597,5 @@ All messages reaching the ``django`` catch-all logger when :setting:`DEBUG` is
599 597
 ``True`` are sent to the console. They are simply discarded (sent to
600 598
 ``NullHandler``) when :setting:`DEBUG` is ``False``.
601 599
 
602  
-.. versionchanged:: 1.5
603  
-
604  
-    Before Django 1.5, all messages reaching the ``django`` logger were
605  
-    discarded, regardless of :setting:`DEBUG`.
606  
-
607 600
 See also :ref:`Configuring logging <configuring-logging>` to learn how you can
608 601
 complement or replace this default logging configuration.
14  docs/topics/pagination.txt
@@ -248,19 +248,13 @@ Methods
248 248
 
249 249
 .. method:: Page.next_page_number()
250 250
 
251  
-    Returns the next page number.
252  
-
253  
-    .. versionchanged:: 1.5
254  
-
255  
-        Raises :exc:`InvalidPage` if next page doesn't exist.
  251
+    Returns the next page number. Raises :exc:`InvalidPage` if next page
  252
+    doesn't exist.
256 253
 
257 254
 .. method:: Page.previous_page_number()
258 255
 
259  
-    Returns the previous page number.
260  
-
261  
-    .. versionchanged:: 1.5
262  
-
263  
-        Raises :exc:`InvalidPage` if previous page doesn't exist.
  256
+    Returns the previous page number. Raises :exc:`InvalidPage` if previous
  257
+    page doesn't exist.
264 258
 
265 259
 .. method:: Page.start_index()
266 260
 
11  docs/topics/serialization.txt
@@ -141,14 +141,11 @@ sure that they are "appropriate" for saving before doing so.  Of course, if you
141 141
 trust your data source you could just save the object and move on.
142 142
 
143 143
 The Django object itself can be inspected as ``deserialized_object.object``.
  144
+If fields in the serialized data do not exist on a model, a
  145
+``DeserializationError`` will be raised unless the ``ignorenonexistent``
  146
+argument is passed in as ``True``::
144 147
 
145  
-.. versionadded:: 1.5
146  
-
147  
-    If fields in the serialized data do not exist on a model,
148  
-    a ``DeserializationError`` will be raised unless the ``ignorenonexistent``
149  
-    argument is passed in as True::
150  
-
151  
-        serializers.deserialize("xml", data, ignorenonexistent=True)
  148
+    serializers.deserialize("xml", data, ignorenonexistent=True)
152 149
 
153 150
 .. _serialization-formats:
154 151
 
4  docs/topics/signals.txt
@@ -132,10 +132,6 @@ Now, our ``my_callback`` function will be called each time a request finishes.
132 132
 Note that ``receiver`` can also take a list of signals to connect a function
133 133
 to.
134 134
 
135  
-.. versionchanged:: 1.5
136  
-
137  
-    The ability to pass a list of signals was added.
138  
-
139 135
 .. admonition:: Where should this code live?
140 136
 
141 137
     You can put signal handling and registration code anywhere you like.
2  docs/topics/testing/advanced.txt
@@ -217,8 +217,6 @@ Advanced features of ``TransactionTestCase``
217 217
 
218 218
 .. attribute:: TransactionTestCase.reset_sequences
219 219
 
220  
-    .. versionadded:: 1.5