Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

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
  • Loading branch information...
commit 2ea93f9327e37c686cc4333d1f483a7c97894a3c 1 parent 00c554f
Tim Graham authored December 26, 2010

Showing 58 changed files with 49 additions and 591 deletions. Show diff stats Hide diff stats

  1. 2  docs/howto/custom-management-commands.txt
  2. 1  docs/howto/custom-model-fields.txt
  3. 8  docs/howto/custom-template-tags.txt
  4. 3  docs/howto/deployment/modpython.txt
  5. 3  docs/intro/tutorial02.txt
  6. 2  docs/ref/authbackends.txt
  7. 2  docs/ref/contrib/admin/actions.txt
  8. 27  docs/ref/contrib/admin/index.txt
  9. 1  docs/ref/contrib/csrf.txt
  10. 2  docs/ref/contrib/flatpages.txt
  11. 2  docs/ref/contrib/formtools/form-wizard.txt
  12. 8  docs/ref/contrib/gis/gdal.txt
  13. 7  docs/ref/contrib/gis/geoquerysets.txt
  14. 88  docs/ref/contrib/gis/geos.txt
  15. 2  docs/ref/contrib/gis/index.txt
  16. 1  docs/ref/contrib/gis/install.txt
  17. 10  docs/ref/contrib/gis/testing.txt
  18. 2  docs/ref/contrib/humanize.txt
  19. 4  docs/ref/contrib/index.txt
  20. 2  docs/ref/contrib/sitemaps.txt
  21. 4  docs/ref/contrib/sites.txt
  22. 8  docs/ref/databases.txt
  23. 16  docs/ref/django-admin.txt
  24. 5  docs/ref/forms/api.txt
  25. 27  docs/ref/forms/fields.txt
  26. 10  docs/ref/forms/widgets.txt
  27. 19  docs/ref/generic-views.txt
  28. 9  docs/ref/middleware.txt
  29. 21  docs/ref/models/fields.txt
  30. 7  docs/ref/models/instances.txt
  31. 8  docs/ref/models/options.txt
  32. 57  docs/ref/models/querysets.txt
  33. 12  docs/ref/request-response.txt
  34. 33  docs/ref/settings.txt
  35. 2  docs/ref/signals.txt
  36. 2  docs/ref/templates/api.txt
  37. 40  docs/ref/templates/builtins.txt
  38. 2  docs/ref/unicode.txt
  39. 13  docs/topics/auth.txt
  40. 14  docs/topics/cache.txt
  41. 2  docs/topics/conditional-view-processing.txt
  42. 2  docs/topics/db/aggregation.txt
  43. 10  docs/topics/db/models.txt
  44. 8  docs/topics/db/queries.txt
  45. 2  docs/topics/db/transactions.txt
  46. 2  docs/topics/email.txt
  47. 2  docs/topics/files.txt
  48. 2  docs/topics/forms/formsets.txt
  49. 7  docs/topics/forms/index.txt
  50. 15  docs/topics/forms/modelforms.txt
  51. 2  docs/topics/http/file-uploads.txt
  52. 31  docs/topics/http/sessions.txt
  53. 2  docs/topics/http/shortcuts.txt
  54. 14  docs/topics/http/urls.txt
  55. 8  docs/topics/i18n/deployment.txt
  56. 3  docs/topics/pagination.txt
  57. 2  docs/topics/templates.txt
  58. 40  docs/topics/testing.txt
2  docs/howto/custom-management-commands.txt
@@ -2,8 +2,6 @@
2 2
 Writing custom django-admin commands
3 3
 ====================================
4 4
 
5  
-.. versionadded:: 1.0
6  
-
7 5
 Applications can register their own actions with ``manage.py``. For example,
8 6
 you might want to add a ``manage.py`` action for a Django app that you're
9 7
 distributing. In this document, we will be building a custom ``closepoll``
1  docs/howto/custom-model-fields.txt
@@ -2,7 +2,6 @@
2 2
 Writing custom model fields
3 3
 ===========================
4 4
 
5  
-.. versionadded:: 1.0
6 5
 .. currentmodule:: django.db.models
7 6
 
8 7
 Introduction
8  docs/howto/custom-template-tags.txt
@@ -155,8 +155,6 @@ will use the function's name as the filter name.
155 155
 Filters and auto-escaping
156 156
 ~~~~~~~~~~~~~~~~~~~~~~~~~
157 157
 
158  
-.. versionadded:: 1.0
159  
-
160 158
 When writing a custom filter, give some thought to how the filter will interact
161 159
 with Django's auto-escaping behavior. Note that three types of strings can be
162 160
 passed around inside the template code:
@@ -426,8 +424,6 @@ without having to be parsed multiple times.
426 424
 Auto-escaping considerations
427 425
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
428 426
 
429  
-.. versionadded:: 1.0
430  
-
431 427
 The output from template tags is **not** automatically run through the
432 428
 auto-escaping filters. However, there are still a couple of things you should
433 429
 keep in mind when writing a template tag.
@@ -605,10 +601,6 @@ Now your tag should begin to look like this::
605 601
             raise template.TemplateSyntaxError, "%r tag's argument should be in quotes" % tag_name
606 602
         return FormatTimeNode(date_to_be_formatted, format_string[1:-1])
607 603
 
608  
-.. versionchanged:: 1.0
609  
-    Variable resolution has changed in the 1.0 release of Django. ``template.resolve_variable()``
610  
-    has been deprecated in favor of a new ``template.Variable`` class.
611  
-
612 604
 You also have to change the renderer to retrieve the actual contents of the
613 605
 ``date_updated`` property of the ``blog_entry`` object.  This can be
614 606
 accomplished by using the ``Variable()`` class in ``django.template``.
3  docs/howto/deployment/modpython.txt
@@ -64,9 +64,6 @@ This tells Apache: "Use mod_python for any URL at or under '/mysite/', using the
64 64
 Django mod_python handler." It passes the value of :ref:`DJANGO_SETTINGS_MODULE
65 65
 <django-settings-module>` so mod_python knows which settings to use.
66 66
 
67  
-.. versionadded:: 1.0
68  
-    The ``PythonOption django.root ...`` is new in this version.
69  
-
70 67
 Because mod_python does not know we are serving this site from underneath the
71 68
 ``/mysite/`` prefix, this value needs to be passed through to the mod_python
72 69
 handler in Django, via the ``PythonOption django.root ...`` line. The value set
3  docs/intro/tutorial02.txt
@@ -38,9 +38,6 @@ activate the admin site for your installation, do these three things:
38 38
       need to know is that it maps URL roots to applications. In the end, you
39 39
       should have a ``urls.py`` file that looks like this:
40 40
 
41  
-    .. versionchanged:: 1.1
42  
-        The method for adding admin urls has changed in Django 1.1.
43  
-
44 41
       .. parsed-literal::
45 42
 
46 43
           from django.conf.urls.defaults import *
2  docs/ref/authbackends.txt
@@ -26,8 +26,6 @@ The following backends are available in :mod:`django.contrib.auth.backends`:
26 26
 
27 27
 .. class:: RemoteUserBackend
28 28
 
29  
-    .. versionadded:: 1.1
30  
-
31 29
     Use this backend to take advantage of external-to-Django-handled
32 30
     authentication.  It authenticates using usernames passed in
33 31
     :attr:`request.META['REMOTE_USER'] <django.http.HttpRequest.META>`.  See
2  docs/ref/contrib/admin/actions.txt
@@ -2,8 +2,6 @@
2 2
 Admin actions
3 3
 =============
4 4
 
5  
-.. versionadded:: 1.1
6  
-
7 5
 .. currentmodule:: django.contrib.admin
8 6
 
9 7
 The basic workflow of Django's admin is, in a nutshell, "select an object,
27  docs/ref/contrib/admin/index.txt
@@ -434,8 +434,6 @@ subclass::
434 434
 
435 435
 .. attribute:: ModelAdmin.list_editable
436 436
 
437  
-    .. versionadded:: 1.1
438  
-
439 437
     Set ``list_editable`` to a list of field names on the model which will
440 438
     allow editing on the change list page. That is, fields listed in
441 439
     ``list_editable`` will be displayed as form widgets on the change list
@@ -678,8 +676,6 @@ subclass::
678 676
 
679 677
 .. attribute:: ModelAdmin.formfield_overrides
680 678
 
681  
-    .. versionadded:: 1.1
682  
-
683 679
     This provides a quick-and-dirty way to override some of the
684 680
     :class:`~django.forms.Field` options for use in the admin.
685 681
     ``formfield_overrides`` is a dictionary mapping a field class to a dict of
@@ -722,16 +718,12 @@ subclass::
722 718
 
723 719
 .. attribute:: ModelAdmin.actions
724 720
 
725  
-    .. versionadded:: 1.1
726  
-
727 721
     A list of actions to make available on the change list page. See
728 722
     :doc:`/ref/contrib/admin/actions` for details.
729 723
 
730 724
 .. attribute:: ModelAdmin.actions_on_top
731 725
 .. attribute:: ModelAdmin.actions_on_bottom
732 726
 
733  
-    .. versionadded:: 1.1
734  
-
735 727
     Controls where on the page the actions bar appears. By default, the admin
736 728
     changelist displays actions at the top of the page (``actions_on_top = True;
737 729
     actions_on_bottom = False``).
@@ -843,8 +835,6 @@ templates used by the :class:`ModelAdmin` views:
843 835
 
844 836
 .. method:: ModelAdmin.get_urls(self)
845 837
 
846  
-    .. versionadded:: 1.1
847  
-
848 838
     The ``get_urls`` method on a ``ModelAdmin`` returns the URLs to be used for
849 839
     that ModelAdmin in the same way as a URLconf.  Therefore you can extend
850 840
     them as documented in :doc:`/topics/http/urls`::
@@ -903,8 +893,6 @@ templates used by the :class:`ModelAdmin` views:
903 893
 
904 894
 .. method:: ModelAdmin.formfield_for_foreignkey(self, db_field, request, **kwargs)
905 895
 
906  
-    .. versionadded:: 1.1
907  
-
908 896
     The ``formfield_for_foreignkey`` method on a ``ModelAdmin`` allows you to
909 897
     override the default formfield for a foreign key field. For example, to
910 898
     return a subset of objects for this foreign key field based on the user::
@@ -920,8 +908,6 @@ templates used by the :class:`ModelAdmin` views:
920 908
 
921 909
 .. method:: ModelAdmin.formfield_for_manytomany(self, db_field, request, **kwargs)
922 910
 
923  
-    .. versionadded:: 1.1
924  
-
925 911
     Like the ``formfield_for_foreignkey`` method, the
926 912
     ``formfield_for_manytomany`` method can be overridden to change the
927 913
     default formfield for a many to many field. For example, if an owner can
@@ -1119,9 +1105,6 @@ adds some of its own (the shared features are actually defined in the
1119 1105
 - :attr:`~ModelAdmin.prepopulated_fields`
1120 1106
 - :attr:`~ModelAdmin.radio_fields`
1121 1107
 - :attr:`~InlineModelAdmin.raw_id_fields`
1122  
-
1123  
-.. versionadded:: 1.1
1124  
-
1125 1108
 - :meth:`~ModelAdmin.formfield_for_foreignkey`
1126 1109
 - :meth:`~ModelAdmin.formfield_for_manytomany`
1127 1110
 
@@ -1512,8 +1495,6 @@ creating your own ``AdminSite`` instance (see below), and changing the
1512 1495
     Python class), and register your models and ``ModelAdmin`` subclasses
1513 1496
     with it instead of using the default.
1514 1497
 
1515  
-    .. versionadded:: 1.1
1516  
-
1517 1498
     When constructing an instance of an ``AdminSite``, you are able to provide
1518 1499
     a unique instance name using the ``name`` argument to the constructor. This
1519 1500
     instance name is used to identify the instance, especially when
@@ -1607,10 +1588,6 @@ It's easy to create multiple instances of the admin site on the same
1607 1588
 Django-powered Web site. Just create multiple instances of ``AdminSite`` and
1608 1589
 root each one at a different URL.
1609 1590
 
1610  
-.. versionchanged:: 1.1
1611  
-    The method for hooking ``AdminSite`` instances into urls has changed in
1612  
-    Django 1.1.
1613  
-
1614 1591
 In this example, the URLs ``/basic-admin/`` and ``/advanced-admin/`` feature
1615 1592
 separate versions of the admin site -- using the ``AdminSite`` instances
1616 1593
 ``myproject.admin.basic_site`` and ``myproject.admin.advanced_site``,
@@ -1633,8 +1610,6 @@ is only necessary if you are using more than one ``AdminSite``.
1633 1610
 Adding views to admin sites
1634 1611
 ---------------------------
1635 1612
 
1636  
-.. versionadded:: 1.1
1637  
-
1638 1613
 Just like :class:`ModelAdmin`, :class:`AdminSite` provides a
1639 1614
 :meth:`~django.contrib.admin.ModelAdmin.get_urls()` method
1640 1615
 that can be overridden to define additional views for the site. To add
@@ -1654,8 +1629,6 @@ a pattern for your new view.
1654 1629
 Reversing Admin URLs
1655 1630
 ====================
1656 1631
 
1657  
-.. versionadded:: 1.1
1658  
-
1659 1632
 When an :class:`AdminSite` is deployed, the views provided by that site are
1660 1633
 accessible using Django's :ref:`URL reversing system <naming-url-patterns>`.
1661 1634
 
1  docs/ref/contrib/csrf.txt
@@ -241,7 +241,6 @@ it.
241 241
 Exceptions
242 242
 ----------
243 243
 
244  
-.. versionadded:: 1.1
245 244
 .. versionchanged:: 1.2
246 245
     Import paths for the decorators below were changed.
247 246
 
2  docs/ref/contrib/flatpages.txt
@@ -17,8 +17,6 @@ custom Django application.
17 17
 A flatpage can use a custom template or a default, systemwide flatpage
18 18
 template. It can be associated with one, or multiple, sites.
19 19
 
20  
-.. versionadded:: 1.0
21  
-
22 20
 The content field may optionally be left blank if you prefer to put your
23 21
 content in a custom template.
24 22
 
2  docs/ref/contrib/formtools/form-wizard.txt
@@ -5,8 +5,6 @@ Form wizard
5 5
 .. module:: django.contrib.formtools.wizard
6 6
     :synopsis: Splits forms across multiple Web pages.
7 7
 
8  
-.. versionadded:: 1.0
9  
-
10 8
 Django comes with an optional "form wizard" application that splits
11 9
 :doc:`forms </topics/forms/index>` across multiple Web pages. It maintains
12 10
 state in hashed HTML :samp:`<input type="hidden">` fields, and the data isn't
8  docs/ref/contrib/gis/gdal.txt
@@ -459,8 +459,6 @@ systems and coordinate transformation::
459 459
 
460 460
    .. classmethod:: from_bbox(bbox)
461 461
 
462  
-   .. versionadded:: 1.1
463  
-
464 462
    Constructs a :class:`Polygon` from the given bounding-box (a 4-tuple).
465 463
 
466 464
    .. method:: __len__
@@ -601,8 +599,6 @@ systems and coordinate transformation::
601 599
 
602 600
    .. attribute:: kml
603 601
 
604  
-   .. versionadded:: 1.1
605  
-
606 602
    Returns a string representation of this geometry in KML format.
607 603
 
608 604
    .. attribute:: wkb_size
@@ -889,8 +885,6 @@ systems and coordinate transformation::
889 885
 
890 886
    .. method:: expand_to_include(self, *args)
891 887
 
892  
-   .. versionadded:: 1.1
893  
-
894 888
 Coordinate System Objects
895 889
 =========================
896 890
 
@@ -992,8 +986,6 @@ Coordinate System Objects
992 986
    Import spatial reference from PROJ.4 string.
993 987
 
994 988
    .. method:: import_user_input(user_input)
995  
-  
996  
-   .. versionadded:: 1.1
997 989
 
998 990
    .. method:: import_wkt(wkt)
999 991
 
7  docs/ref/contrib/gis/geoquerysets.txt
@@ -835,8 +835,6 @@ Reverse the coordinate order of the geometry field, and attaches as a
835 835
 
836 836
 .. method:: GeoQuerySet.snap_to_grid(*args, **kwargs)
837 837
 
838  
-.. versionadded:: 1.1
839  
-
840 838
 Snap all points of the input geometry to the grid.  How the
841 839
 geometry is snapped to the grid depends on how many numeric
842 840
 (either float, integer, or long) arguments are given.
@@ -957,8 +955,6 @@ __ http://geohash.org/
957 955
 
958 956
 .. method:: GeoQuerySet.geojson(**kwargs)
959 957
 
960  
-.. versionadded:: 1.1
961  
-
962 958
 *Availability*: PostGIS
963 959
 
964 960
 Attaches a ``geojson`` attribute to every model in the queryset that contains the
@@ -1102,7 +1098,6 @@ the ``GeoQuerySet``; otherwise sets with ``None``.
1102 1098
 
1103 1099
 Spatial Aggregates
1104 1100
 ==================
1105  
-.. versionadded:: 1.1
1106 1101
 
1107 1102
 Aggregate Methods
1108 1103
 -----------------
@@ -1112,8 +1107,6 @@ Aggregate Methods
1112 1107
 
1113 1108
 .. method:: GeoQuerySet.collect(**kwargs)
1114 1109
 
1115  
-.. versionadded:: 1.1
1116  
-
1117 1110
 *Availability*: PostGIS
1118 1111
 
1119 1112
 Returns a ``GEOMETRYCOLLECTION`` or a ``MULTI`` geometry object from the geometry
88  docs/ref/contrib/gis/geos.txt
@@ -33,10 +33,10 @@ features include:
33 33
 * A BSD-licensed interface to the GEOS geometry routines, implemented purely
34 34
   in Python using ``ctypes``.
35 35
 * Loosely-coupled to GeoDjango.  For example, :class:`GEOSGeometry` objects
36  
-  may be used outside of a django project/application.  In other words, 
  36
+  may be used outside of a django project/application.  In other words,
37 37
   no need to have ``DJANGO_SETTINGS_MODULE`` set or use a database, etc.
38 38
 * Mutability: :class:`GEOSGeometry` objects may be modified.
39  
-* Cross-platform and tested; compatible with Windows, Linux, Solaris, and Mac 
  39
+* Cross-platform and tested; compatible with Windows, Linux, Solaris, and Mac
40 40
   OS X platforms.
41 41
 
42 42
 .. _geos-tutorial:
@@ -44,7 +44,7 @@ features include:
44 44
 Tutorial
45 45
 ========
46 46
 
47  
-This section contains a brief introduction and tutorial to using 
  47
+This section contains a brief introduction and tutorial to using
48 48
 :class:`GEOSGeometry` objects.
49 49
 
50 50
 Creating a Geometry
@@ -75,7 +75,7 @@ return a :class:`GEOSGeometry` object from an input string or a file::
75 75
     >>> pnt = fromfile('/path/to/pnt.wkt')
76 76
     >>> pnt = fromfile(open('/path/to/pnt.wkt'))
77 77
 
78  
-Geometries are Pythonic 
  78
+Geometries are Pythonic
79 79
 -----------------------
80 80
 :class:`GEOSGeometry` objects are 'Pythonic', in other words components may
81 81
 be accessed, modified, and iterated over using standard Python conventions.
@@ -146,7 +146,7 @@ are accepted:
146 146
 =============  ======================
147 147
 Format         Input Type
148 148
 =============  ======================
149  
-WKT / EWKT     ``str`` or ``unicode`` 
  149
+WKT / EWKT     ``str`` or ``unicode``
150 150
 HEX / HEXEWKB  ``str`` or ``unicode``
151 151
 WKB / EWKB     ``buffer``
152 152
 GeoJSON        ``str`` or ``unicode``
@@ -161,7 +161,7 @@ Returns the coordinates of the geometry as a tuple.
161 161
 
162 162
 .. attribute:: GEOSGeometry.empty
163 163
 
164  
-Returns whether or not the set of points in the geometry is empty. 
  164
+Returns whether or not the set of points in the geometry is empty.
165 165
 
166 166
 .. attribute:: GEOSGeometry.geom_type
167 167
 
@@ -219,11 +219,11 @@ definition.
219 219
 
220 220
 Returns a boolean indicating whether the geometry is valid.
221 221
 
222  
-.. attribute:: GEOSGeometry.valid_reason 
  222
+.. attribute:: GEOSGeometry.valid_reason
223 223
 
224  
-.. versionadded:: 1.3 
  224
+.. versionadded:: 1.3
225 225
 
226  
-Returns a string describing the reason why a geometry is invalid. 
  226
+Returns a string describing the reason why a geometry is invalid.
227 227
 
228 228
 .. attribute:: GEOSGeometry.srid
229 229
 
@@ -248,27 +248,27 @@ another object.
248 248
 
249 249
 Returns the "extended" Well-Known Text of the geometry.  This representation
250 250
 is specific to PostGIS and is a super set of the OGC WKT standard. [#fnogc]_
251  
-Essentially the SRID is prepended to the WKT representation, for example 
252  
-``SRID=4326;POINT(5 23)``. 
  251
+Essentially the SRID is prepended to the WKT representation, for example
  252
+``SRID=4326;POINT(5 23)``.
253 253
 
254 254
 .. note::
255 255
 
256  
-   The output from this property does not include the 3dm, 3dz, and 4d 
  256
+   The output from this property does not include the 3dm, 3dz, and 4d
257 257
    information that PostGIS supports in its EWKT representations.
258 258
 
259 259
 .. attribute:: GEOSGeometry.hex
260 260
 
261 261
 Returns the WKB of this Geometry in hexadecimal form.  Please note
262 262
 that the SRID and Z values are not included in this representation
263  
-because it is not a part of the OGC specification (use the 
  263
+because it is not a part of the OGC specification (use the
264 264
 :attr:`GEOSGeometry.hexewkb` property instead).
265 265
 
266 266
 .. attribute:: GEOSGeometry.hexewkb
267 267
 
268 268
 .. versionadded:: 1.2
269 269
 
270  
-Returns the EWKB of this Geometry in hexadecimal form.  This is an 
271  
-extension of the WKB specification that includes SRID and Z values 
  270
+Returns the EWKB of this Geometry in hexadecimal form.  This is an
  271
+extension of the WKB specification that includes SRID and Z values
272 272
 that are a part of this geometry.
273 273
 
274 274
 .. note::
@@ -290,12 +290,12 @@ Alias for :attr:`GEOSGeometry.json`.
290 290
 .. attribute:: GEOSGeometry.kml
291 291
 
292 292
 Returns a `KML`__ (Keyhole Markup Language) representation of the
293  
-geometry.  This should only be used for geometries with an SRID of 
  293
+geometry.  This should only be used for geometries with an SRID of
294 294
 4326 (WGS84), but this restriction is not enforced.
295 295
 
296 296
 .. attribute:: GEOSGeometry.ogr
297 297
 
298  
-Returns an :class:`~django.contrib.gis.gdal.OGRGeometry` object 
  298
+Returns an :class:`~django.contrib.gis.gdal.OGRGeometry` object
299 299
 correspondg to the GEOS geometry.
300 300
 
301 301
 .. note::
@@ -344,7 +344,7 @@ Returns ``True`` if :meth:`GEOSGeometry.within` is ``False``.
344 344
 .. method:: GEOSGeometry.crosses(other)
345 345
 
346 346
 Returns ``True`` if the DE-9IM intersection matrix for the two Geometries
347  
-is ``T*T******`` (for a point and a curve,a point and an area or a line 
  347
+is ``T*T******`` (for a point and a curve,a point and an area or a line
348 348
 and an area) ``0********`` (for two curves).
349 349
 
350 350
 .. method:: GEOSGeometry.disjoint(other)
@@ -354,7 +354,7 @@ is ``FF*FF****``.
354 354
 
355 355
 .. method:: GEOSGeometry.equals(other)
356 356
 
357  
-Returns ``True`` if the DE-9IM intersection matrix for the two geometries 
  357
+Returns ``True`` if the DE-9IM intersection matrix for the two geometries
358 358
 is ``T*F**FFF*``.
359 359
 
360 360
 .. method:: GEOSGeometry.equals_exact(other, tolerance=0)
@@ -377,8 +377,8 @@ is ``T*T***T**`` (for two points or two surfaces) ``1*T***T**``
377 377
 
378 378
 .. method:: GEOSGeometry.relate_pattern(other, pattern)
379 379
 
380  
-Returns ``True`` if the elements in the DE-9IM intersection matrix 
381  
-for this geometry and the other matches the given ``pattern`` -- 
  380
+Returns ``True`` if the elements in the DE-9IM intersection matrix
  381
+for this geometry and the other matches the given ``pattern`` --
382 382
 a string of nine characters from the alphabet: {``T``, ``F``, ``*``, ``0``}.
383 383
 
384 384
 .. method:: GEOSGeometry.touches(other)
@@ -397,8 +397,8 @@ Topological Methods
397 397
 .. method:: GEOSGeometry.buffer(width, quadsegs=8)
398 398
 
399 399
 Returns a :class:`GEOSGeometry` that represents all points whose distance
400  
-from this geometry is less than or equal to the given ``width``. The optional 
401  
-``quadsegs`` keyword sets the number of segments used to approximate a 
  400
+from this geometry is less than or equal to the given ``width``. The optional
  401
+``quadsegs`` keyword sets the number of segments used to approximate a
402 402
 quarter circle (defaults is 8).
403 403
 
404 404
 .. method:: GEOSGeometry.difference(other)
@@ -423,21 +423,21 @@ algorithm to the specified tolerance.  A higher tolerance value implies
423 423
 less points in the output.  If no tolerance is tolerance provided,
424 424
 it defaults to 0.
425 425
 
426  
-By default, this function does not preserve topology - e.g., 
  426
+By default, this function does not preserve topology - e.g.,
427 427
 :class:`Polygon` objects can be split, collapsed into lines or disappear.
428 428
 :class:`Polygon` holes can be created or disappear, and lines can cross.
429 429
 By specifying ``preserve_topology=True``, the result will have the same
430  
-dimension and number of components as the input, however, this is 
431  
-significantly slower.   
  430
+dimension and number of components as the input, however, this is
  431
+significantly slower.
432 432
 
433 433
 .. method:: GEOSGeometry.sym_difference(other)
434 434
 
435  
-Returns a :class:`GEOSGeometry` combining the points in this geometry 
  435
+Returns a :class:`GEOSGeometry` combining the points in this geometry
436 436
 not in other, and the points in other not in this geometry.
437 437
 
438 438
 .. method:: GEOSGeometry.union(other)
439 439
 
440  
-Returns a :class:`GEOSGeometry` representing all the points in this 
  440
+Returns a :class:`GEOSGeometry` representing all the points in this
441 441
 geometry and the other.
442 442
 
443 443
 Topological Properties
@@ -477,7 +477,7 @@ This property returns the area of the Geometry.
477 477
 
478 478
 .. attribute:: GEOSGeometry.extent
479 479
 
480  
-This property returns the extent of this geometry as a 4-tuple, 
  480
+This property returns the extent of this geometry as a 4-tuple,
481 481
 consisting of (xmin, ymin, xmax, ymax).
482 482
 
483 483
 .. method:: GEOSGeometry.clone()
@@ -492,24 +492,22 @@ Returns the distance between the closest points on this geometry and the given
492 492
 .. note::
493 493
 
494 494
     GEOS distance calculations are  linear -- in other words, GEOS does not
495  
-    perform a spherical calculation even if the SRID specifies a geographic 
  495
+    perform a spherical calculation even if the SRID specifies a geographic
496 496
     coordinate system.
497 497
 
498 498
 .. attribute:: GEOSGeometry.length
499 499
 
500  
-Returns the length of this geometry (e.g., 0 for a :class:`Point`, 
501  
-the length of a :class:`LineString`, or the circumference of 
  500
+Returns the length of this geometry (e.g., 0 for a :class:`Point`,
  501
+the length of a :class:`LineString`, or the circumference of
502 502
 a :class:`Polygon`).
503 503
 
504 504
 .. attribute:: GEOSGeometry.prepared
505 505
 
506  
-.. versionadded:: 1.1
507  
-
508 506
 .. note::
509 507
 
510 508
     Support for prepared geometries requires GEOS 3.1.
511 509
 
512  
-Returns a GEOS ``PreparedGeometry`` for the contents of this geometry.  
  510
+Returns a GEOS ``PreparedGeometry`` for the contents of this geometry.
513 511
 ``PreparedGeometry`` objects are optimized for the contains, intersects,
514 512
 and covers operations.  Refer to the :ref:`prepared-geometries` documentation
515 513
 for more information.
@@ -529,7 +527,7 @@ corresponding to the SRID of the geometry or ``None``.
529 527
 
530 528
 Transforms the geometry according to the given coordinate transformation paramter
531 529
 (``ct``), which may be an integer SRID, spatial reference WKT string,
532  
-a PROJ.4 string, a :class:`~django.contrib.gis.gdal.SpatialReference` object, or a 
  530
+a PROJ.4 string, a :class:`~django.contrib.gis.gdal.SpatialReference` object, or a
533 531
 :class:`~django.contrib.gis.gdal.CoordTransform` object. By default, the geometry
534 532
 is transformed in-place and nothing is returned. However if the ``clone`` keyword
535 533
 is set, then the geometry is not modified and a transformed clone of the geometry
@@ -611,8 +609,6 @@ is returned instead.
611 609
 
612 610
    .. classmethod:: from_bbox(bbox)
613 611
 
614  
-   .. versionadded:: 1.1
615  
-
616 612
    Returns a polygon object from the given bounding-box, a 4-tuple
617 613
    comprising (xmin, ymin, xmax, ymax).
618 614
 
@@ -651,11 +647,9 @@ Geometry Collections
651 647
 
652 648
    .. attribute:: merged
653 649
 
654  
-   .. versionadded:: 1.1
655  
-
656 650
    Returns a :class:`LineString` representing the line merge of
657 651
    all the components in this ``MultiLineString``.
658  
-       
  652
+
659 653
 
660 654
 ``MultiPolygon``
661 655
 ----------------
@@ -673,8 +667,6 @@ Geometry Collections
673 667
 
674 668
    .. attribute:: cascaded_union
675 669
 
676  
-   .. versionadded:: 1.1
677  
-
678 670
    Returns a :class:`Polygon` that is the union of all of the component
679 671
    polygons in this collection.  The algorithm employed is significantly
680 672
    more efficient (faster) than trying to union the geometries together
@@ -702,13 +694,11 @@ Geometry Collections
702 694
 Prepared Geometries
703 695
 ===================
704 696
 
705  
-.. versionadded: 1.1
706  
-
707 697
 In order to obtain a prepared geometry, just access the
708 698
 :attr:`GEOSGeometry.prepared` property.  Once you have a
709 699
 ``PreparedGeometry`` instance its spatial predicate methods, listed below,
710 700
 may be used with other ``GEOSGeometry`` objects.  An operation with a prepared
711  
-geometry can be orders of magnitude faster -- the more complex the geometry 
  701
+geometry can be orders of magnitude faster -- the more complex the geometry
712 702
 that is prepared, the larger the speedup in the operation.  For more information,
713 703
 please consult the `GEOS wiki page on prepared geometries <http://trac.osgeo.org/geos/wiki/PreparedGeometry>`_.
714 704
 
@@ -770,8 +760,6 @@ Example::
770 760
 I/O Objects
771 761
 ===========
772 762
 
773  
-.. versionadded: 1.1
774  
-
775 763
 Reader Objects
776 764
 --------------
777 765
 
@@ -807,7 +795,7 @@ include the SRID and 3D values (in other words, EWKB).
807 795
 .. class:: WKBWriter
808 796
 
809 797
 ``WKBWriter`` provides the most control over its output.  By default it
810  
-returns OGC-compliant WKB when it's ``write`` method is called.  However, 
  798
+returns OGC-compliant WKB when it's ``write`` method is called.  However,
811 799
 it has properties that allow for the creation of EWKB, a superset of the
812 800
 WKB standard that includes additional information.
813 801
 
@@ -925,5 +913,5 @@ location (e.g., ``/home/bob/lib/libgeos_c.so``).
925 913
 
926 914
 .. note::
927 915
 
928  
-    The setting must be the *full* path to the **C** shared library; in 
  916
+    The setting must be the *full* path to the **C** shared library; in
929 917
     other words you want to use ``libgeos_c.so``, not ``libgeos.so``.
2  docs/ref/contrib/gis/index.txt
@@ -4,8 +4,6 @@
4 4
 GeoDjango
5 5
 =========
6 6
 
7  
-.. versionadded:: 1.0
8  
-
9 7
 .. module:: django.contrib.gis
10 8
    :synopsis: Geographic Information System (GIS) extensions for Django
11 9
 
1  docs/ref/contrib/gis/install.txt
@@ -357,7 +357,6 @@ file::
357 357
 
358 358
 SpatiaLite
359 359
 ----------
360  
-.. versionadded:: 1.1
361 360
 
362 361
 .. note::
363 362
 
10  docs/ref/contrib/gis/testing.txt
@@ -28,8 +28,6 @@ Settings
28 28
 ``POSTGIS_TEMPLATE``
29 29
 ^^^^^^^^^^^^^^^^^^^^
30 30
 
31  
-.. versionadded:: 1.1
32  
-
33 31
 .. versionchanged:: 1.2
34 32
 
35 33
 This setting may be used to customize the name of the PostGIS template
@@ -42,8 +40,6 @@ defaults to ``'template_postgis'`` (the same name used in the
42 40
 ``POSTGIS_VERSION``
43 41
 ^^^^^^^^^^^^^^^^^^^
44 42
 
45  
-.. versionadded:: 1.1
46  
-
47 43
 When GeoDjango's spatial backend initializes on PostGIS, it has to perform
48 44
 a SQL query to determine the version in order to figure out what
49 45
 features are available.  Advanced users wishing to prevent this additional
@@ -118,8 +114,6 @@ spatial database entitled ``template_postgis``.
118 114
 SpatiaLite
119 115
 ==========
120 116
 
121  
-.. versionadded:: 1.1
122  
-
123 117
 You will need to download the `initialization SQL`__ script for SpatiaLite::
124 118
 
125 119
     $ wget http://www.gaia-gis.it/spatialite/init_spatialite-2.3.zip
@@ -138,8 +132,6 @@ Settings
138 132
 ``SPATIALITE_SQL``
139 133
 ^^^^^^^^^^^^^^^^^^
140 134
 
141  
-.. versionadded:: 1.1
142  
-
143 135
 By default, the GeoDjango test runner looks for the SpatiaLite SQL in the
144 136
 same directory where it was invoked (by default the same directory where
145 137
 ``manage.py`` is located).  If you want to use a different location, then
@@ -201,7 +193,7 @@ all of the databases in the settings file must be using one of the
201 193
 
202 194
 .. warning::
203 195
 
204  
-    Do not change the :setting:`TEST_RUNNER` setting 
  196
+    Do not change the :setting:`TEST_RUNNER` setting
205 197
     when running the GeoDjango tests with ``runtests.py``.
206 198
 
207 199
 Example
2  docs/ref/contrib/humanize.txt
@@ -68,8 +68,6 @@ You can pass in either an integer or a string representation of an integer.
68 68
 naturalday
69 69
 ----------
70 70
 
71  
-.. versionadded:: 1.0
72  
-
73 71
 For dates that are the current day or within one day, return "today",
74 72
 "tomorrow" or "yesterday", as appropriate. Otherwise, format the date using
75 73
 the passed in format string.
4  docs/ref/contrib/index.txt
@@ -61,10 +61,6 @@ See :doc:`/topics/auth`.
61 61
 comments
62 62
 ========
63 63
 
64  
-.. versionchanged:: 1.0
65  
-   The comments application has been rewriten. See :doc:`/ref/contrib/comments/upgrade`
66  
-   for information on howto upgrade.
67  
-
68 64
 A simple yet flexible comments system. See :doc:`/ref/contrib/comments/index`.
69 65
 
70 66
 contenttypes
2  docs/ref/contrib/sitemaps.txt
@@ -365,8 +365,6 @@ Pinging Google via `manage.py`
365 365
 
366 366
 .. django-admin:: ping_google
367 367
 
368  
-.. versionadded:: 1.0
369  
-
370 368
 Once the sitemaps application is added to your project, you may also
371 369
 ping Google using the ``ping_google`` management command::
372 370
 
4  docs/ref/contrib/sites.txt
@@ -240,8 +240,6 @@ To do this, you can use the sites framework. A simple example::
240 240
 Caching the current ``Site`` object
241 241
 ===================================
242 242
 
243  
-.. versionadded:: 1.0
244  
-
245 243
 As the current site is stored in the database, each call to
246 244
 ``Site.objects.get_current()`` could result in a database query. But Django is a
247 245
 little cleverer than that: on the first request, the current site is cached, and
@@ -395,8 +393,6 @@ Here's how Django uses the sites framework:
395 393
 
396 394
 .. _requestsite-objects:
397 395
 
398  
-.. versionadded:: 1.0
399  
-
400 396
 Some :doc:`django.contrib </ref/contrib/index>` applications take advantage of
401 397
 the sites framework but are architected in a way that doesn't *require* the
402 398
 sites framework to be installed in your database. (Some people don't want to, or
8  docs/ref/databases.txt
@@ -58,8 +58,6 @@ as any other Django backend in this respect.
58 58
 Autocommit mode
59 59
 ~~~~~~~~~~~~~~~
60 60
 
61  
-.. versionadded:: 1.1
62  
-
63 61
 If your application is particularly read-heavy and doesn't make many
64 62
 database writes, the overhead of a constantly open transaction can
65 63
 sometimes be noticeable. For those situations, if you're using the
@@ -101,8 +99,6 @@ protection for multi-call operations.
101 99
 Indexes for ``varchar`` and ``text`` columns
102 100
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
103 101
 
104  
-.. versionadded:: 1.1.2
105  
-
106 102
 When specifying ``db_index=True`` on your model fields, Django typically
107 103
 outputs a single ``CREATE INDEX`` statement.  However, if the database type
108 104
 for the field is either ``varchar`` or ``text`` (e.g., used by ``CharField``,
@@ -454,8 +450,6 @@ version of SQLite.
454 450
 Using newer versions of the SQLite DB-API 2.0 driver
455 451
 ----------------------------------------------------
456 452
 
457  
-.. versionadded:: 1.1
458  
-
459 453
 For versions of Python 2.5 or newer that include ``sqlite3`` in the standard
460 454
 library Django will now use a ``pysqlite2`` interface in preference to
461 455
 ``sqlite3`` if it finds one is available.
@@ -637,8 +631,6 @@ many-to-many table would be stored in the ``indexes`` tablespace. The ``data``
637 631
 field would also generate an index, but no tablespace for it is specified, so
638 632
 it would be stored in the model tablespace ``tables`` by default.
639 633
 
640  
-.. versionadded:: 1.0
641  
-
642 634
 Use the :setting:`DEFAULT_TABLESPACE` and :setting:`DEFAULT_INDEX_TABLESPACE`
643 635
 settings to specify default values for the db_tablespace options.
644 636
 These are useful for setting a tablespace for the built-in Django apps and
16  docs/ref/django-admin.txt
@@ -88,8 +88,6 @@ cleanup
88 88
 
89 89
 .. django-admin:: cleanup
90 90
 
91  
-.. versionadded:: 1.0
92  
-
93 91
 Can be run as a cronjob or directly to clean out old data from the database
94 92
 (only expired sessions at the moment).
95 93
 
@@ -98,9 +96,6 @@ compilemessages
98 96
 
99 97
 .. django-admin:: compilemessages
100 98
 
101  
-.. versionchanged:: 1.0
102  
-   Before 1.0 this was the "bin/compile-messages.py" command.
103  
-
104 99
 Compiles .po files created with ``makemessages`` to .mo files for use with
105 100
 the builtin gettext support. See :doc:`/topics/i18n/index`.
106 101
 
@@ -197,8 +192,6 @@ By default, ``dumpdata`` will output all data on a single line. This isn't
197 192
 easy for humans to read, so you can use the ``--indent`` option to
198 193
 pretty-print the output with a number of indentation spaces.
199 194
 
200  
-.. versionadded:: 1.0
201  
-
202 195
 The :djadminopt:`--exclude` option may be provided to prevent specific
203 196
 applications from being dumped.
204 197
 
@@ -207,8 +200,6 @@ applications from being dumped.
207 200
 The :djadminopt:`--exclude` option may also be provided to prevent specific
208 201
 models (specified as in the form of ``appname.ModelName``) from being dumped.
209 202
 
210  
-.. versionadded:: 1.1
211  
-
212 203
 In addition to specifying application names, you can provide a list of
213 204
 individual models, in the form of ``appname.Model``. If you specify a model
214 205
 name to ``dumpdata``, the dumped output will be restricted to that model,
@@ -406,9 +397,6 @@ makemessages
406 397
 
407 398
 .. django-admin:: makemessages
408 399
 
409  
-.. versionchanged:: 1.0
410  
-   Before 1.0 this was the ``bin/make-messages.py`` command.
411  
-
412 400
 Runs over the entire source tree of the current directory and pulls out all
413 401
 strings marked for translation. It creates (or updates) a message file in the
414 402
 conf/locale (in the django tree) or locale (for project and application)
@@ -963,8 +951,6 @@ testserver <fixture fixture ...>
963 951
 
964 952
 .. django-admin:: testserver
965 953
 
966  
-.. versionadded:: 1.0
967  
-
968 954
 Runs a Django development server (as in ``runserver``) using data from the
969 955
 given fixture(s).
970 956
 
@@ -1067,8 +1053,6 @@ createsuperuser
1067 1053
 
1068 1054
 .. django-admin:: createsuperuser
1069 1055
 
1070  
-.. versionadded:: 1.0
1071  
-
1072 1056
 This command is only available if Django's :doc:`authentication system
1073 1057
 </topics/auth>` (``django.contrib.auth``) is installed.
1074 1058
 
5  docs/ref/forms/api.txt
@@ -195,9 +195,6 @@ it, you can access the clean data via its ``cleaned_data`` attribute::
195 195
     >>> f.cleaned_data
196 196
     {'cc_myself': True, 'message': u'Hi there', 'sender': u'foo@example.com', 'subject': u'hello'}
197 197
 
198  
-.. versionchanged:: 1.0
199  
-    The ``cleaned_data`` attribute was called ``clean_data`` in earlier releases.
200  
-
201 198
 Note that any text-based field -- such as ``CharField`` or ``EmailField`` --
202 199
 always cleans the input into a Unicode string. We'll cover the encoding
203 200
 implications later in this document.
@@ -680,8 +677,6 @@ by a ``Widget``::
680 677
 Binding uploaded files to a form
681 678
 --------------------------------
682 679
 
683  
-.. versionadded:: 1.0
684  
-
685 680
 Dealing with forms that have ``FileField`` and ``ImageField`` fields
686 681
 is a little more complicated than a normal form.
687 682
 
27  docs/ref/forms/fields.txt
@@ -230,8 +230,6 @@ fields. We've specified ``auto_id=False`` to simplify the output::
230 230
 ``error_messages``
231 231
 ~~~~~~~~~~~~~~~~~~
232 232
 
233  
-.. versionadded:: 1.0
234  
-
235 233
 .. attribute:: Field.error_messages
236 234
 
237 235
 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
303 301
       the field has ``required=True``.
304 302
     * Error message keys: ``required``
305 303
 
306  
-.. versionchanged:: 1.0
307  
-   The empty value for a ``CheckboxInput`` (and hence the standard
308  
-   ``BooleanField``) has changed to return ``False`` instead of ``None`` in
309  
-   the Django 1.0.
310  
-
311 304
 .. note::
312 305
 
313 306
     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::
411 404
     '%B %d %Y', '%B %d, %Y',            # 'October 25 2006', 'October 25, 2006'
412 405
     '%d %B %Y', '%d %B, %Y',            # '25 October 2006', '25 October, 2006'
413 406
 
414  
-.. versionchanged:: 1.1
415  
-   The ``DateField`` previously used a ``TextInput`` widget by default. It now
416  
-   uses a ``DateInput`` widget.
417  
-
418 407
 ``DateTimeField``
419 408
 ~~~~~~~~~~~~~~~~~
420 409
 
@@ -446,14 +435,9 @@ If no ``input_formats`` argument is provided, the default input formats are::
446 435
     '%m/%d/%y %H:%M',        # '10/25/06 14:30'
447 436
     '%m/%d/%y',              # '10/25/06'
448 437
 
449  
-.. versionchanged:: 1.0
450  
-   The ``DateTimeField`` used to use a ``TextInput`` widget by default. This has now changed.
451  
-
452 438
 ``DecimalField``
453 439
 ~~~~~~~~~~~~~~~~
454 440
 
455  
-.. versionadded:: 1.0
456  
-
457 441
 .. class:: DecimalField(**kwargs)
458 442
 
459 443
     * Default widget: ``TextInput``
@@ -506,8 +490,6 @@ given length.
506 490
 ``FileField``
507 491
 ~~~~~~~~~~~~~
508 492
 
509  
-.. versionadded:: 1.0
510  
-
511 493
 .. class:: FileField(**kwargs)
512 494
 
513 495
     * Default widget: ``ClearableFileInput``
@@ -526,8 +508,6 @@ When you use a ``FileField`` in a form, you must also remember to
526 508
 ``FilePathField``
527 509
 ~~~~~~~~~~~~~~~~~
528 510
 
529  
-.. versionadded:: 1.0
530  
-
531 511
 .. class:: FilePathField(**kwargs)
532 512
 
533 513
     * Default widget: ``Select``
@@ -572,8 +552,6 @@ These control the range of values permitted in the field.
572 552
 ``ImageField``
573 553
 ~~~~~~~~~~~~~~
574 554
 
575  
-.. versionadded:: 1.0
576  
-
577 555
 .. class:: ImageField(**kwargs)
578 556
 
579 557
     * Default widget: ``ClearableFileInput``
@@ -855,11 +833,6 @@ for ``DateField`` are used.
855 833
 If no ``input_time_formats`` argument is provided, the default input formats
856 834
 for ``TimeField`` are used.
857 835
 
858  
-.. versionchanged:: 1.1
859  
-   The ``SplitDateTimeField`` previously used two ``TextInput`` widgets by
860  
-   default. The ``input_date_formats`` and ``input_time_formats`` arguments
861  
-   are also new.
862  
-
863 836
 Fields which handle relationships
864 837
 ---------------------------------
865 838
 
10  docs/ref/forms/widgets.txt
@@ -56,8 +56,6 @@ commonly used groups of widgets:
56 56
 
57 57
 .. class:: DateInput
58 58
 
59  
-    .. versionadded:: 1.1
60  
-
61 59
     Date input as a simple text box: ``<input type='text' ...>``
62 60
 
63 61
     Takes one optional argument:
@@ -70,8 +68,6 @@ commonly used groups of widgets:
70 68
 
71 69
 .. class:: DateTimeInput
72 70
 
73  
-    .. versionadded:: 1.0
74  
-
75 71
     Date/time input as a simple text box: ``<input type='text' ...>``
76 72
 
77 73
     Takes one optional argument:
@@ -95,9 +91,6 @@ commonly used groups of widgets:
95 91
 
96 92
     If no ``format`` argument is provided, the default format is ``'%H:%M:%S'``.
97 93
 
98  
-    .. versionchanged:: 1.1
99  
-       The ``format`` argument was not supported in Django 1.0.
100  
-
101 94
 .. class:: Textarea
102 95
 
103 96
     Text area: ``<textarea>...</textarea>``
@@ -167,9 +160,6 @@ commonly used groups of widgets:
167 160
     Takes two optional arguments, ``date_format`` and ``time_format``, which
168 161
     work just like the ``format`` argument for ``DateInput`` and ``TimeInput``.
169 162
 
170  
-    .. versionchanged:: 1.1
171  
-       The ``date_format`` and ``time_format`` arguments were not supported in Django 1.0.
172  
-
173 163
 .. class:: SelectDateWidget
174 164
 
175 165
     Wrapper around three select widgets: one each for month, day, and year.
19  docs/ref/generic-views.txt
@@ -93,9 +93,6 @@ If the given URL is ``None``, Django will return an ``HttpResponseGone`` (410).
93 93
       to the URL. If ``False``, then the query string is discarded. By
94 94
       default, ``query_string`` is ``False``.
95 95
 
96  
-.. versionadded:: 1.1
97  
-    The ``permanent`` keyword argument is new in Django 1.1.
98  
-
99 96
 .. versionadded:: 1.3
100 97
     The ``query_string`` keyword argument is new in Django 1.3.
101 98
 
@@ -184,8 +181,6 @@ a date in the *future* are not included unless you set ``allow_future`` to
184 181
       specified in ``date_field`` is greater than the current date/time. By
185 182
       default, this is ``False``.
186 183
 
187  
-    .. versionadded:: 1.0
188  
-
189 184
     * ``template_object_name``: Designates the name of the template variable
190 185
       to use in the template context. By default, this is ``'latest'``.
191 186
 
@@ -210,9 +205,6 @@ In addition to ``extra_context``, the template's context will be:
210 205
       ``datetime.datetime`` objects. These are ordered in reverse. This is
211 206
       equivalent to ``queryset.dates(date_field, 'year')[::-1]``.
212 207
 
213  
-    .. versionchanged:: 1.0
214  
-       The behaviour depending on ``template_object_name`` is new in this version.
215  
-
216 208
     * ``latest``: The ``num_latest`` objects in the system, ordered descending
217 209
       by ``date_field``. For example, if ``num_latest`` is ``10``, then
218 210
       ``latest`` will be a list of the latest 10 objects in ``queryset``.
@@ -729,9 +721,6 @@ If ``template_name`` isn't specified, this view will use the template
729 721
 
730 722
 **Template context:**
731 723
 
732  
-.. versionadded:: 1.0
733  
-   The ``paginator`` and ``page_obj`` context variables are new.
734  
-
735 724
 In addition to ``extra_context``, the template's context will be:
736 725
 
737 726
     * ``object_list``: The list of objects. This variable's name depends on the
@@ -775,8 +764,6 @@ represented as page ``1``.
775 764
 For more on pagination, read the :doc:`pagination documentation
776 765
 </topics/pagination>`.
777 766
 
778  
-.. versionadded:: 1.0
779  
-
780 767
 As a special case, you are also permitted to use ``last`` as a value for
781 768
 ``page``::
782 769
 
@@ -861,12 +848,6 @@ Create/update/delete generic views
861 848
 The ``django.views.generic.create_update`` module contains a set of functions
862 849
 for creating, editing and deleting objects.
863 850
 
864  
-.. versionchanged:: 1.0
865  
-
866  
-``django.views.generic.create_update.create_object`` and
867  
-``django.views.generic.create_update.update_object`` now use the new :doc:`forms
868  
-library </topics/forms/index>` to build and display the form.
869  
-
870 851
 ``django.views.generic.create_update.create_object``
871 852
 ----------------------------------------------------
872 853
 
9  docs/ref/middleware.txt
@@ -52,11 +52,6 @@ Adds a few conveniences for perfectionists:
52 52
       you don't have a valid URL pattern for ``foo.com/bar`` but *do* have a
53 53
       valid pattern for ``foo.com/bar/``.
54 54
 
55  
-      .. versionchanged:: 1.0
56  
-         The behavior of :setting:`APPEND_SLASH` has changed slightly in this
57  
-         version. It didn't used to check whether the pattern was matched in
58  
-         the URLconf.
59  
-
60 55
       If :setting:`PREPEND_WWW` is ``True``, URLs that lack a leading "www."
61 56
       will be redirected to the same URL with a leading "www."
62 57
 
@@ -123,8 +118,6 @@ Reverse proxy middleware
123 118
 
124 119
 .. class:: SetRemoteAddrFromForwardedFor
125 120
 
126  
-.. versionchanged:: 1.1
127  
-
128 121
 This middleware was removed in Django 1.1. See :ref:`the release notes
129 122
 <removed-setremoteaddrfromforwardedfor-middleware>` for details.
130 123
 
@@ -186,8 +179,6 @@ CSRF protection middleware
186 179
 
187 180
 .. class:: CsrfMiddleware
188 181
 
189  
-.. versionadded:: 1.0
190  
-
191 182
 Adds protection against Cross Site Request Forgeries by adding hidden form
192 183
 fields to POST forms and checking requests for the correct value. See the
193 184
 :doc:`Cross Site Request Forgery protection documentation </ref/contrib/csrf>`.
21  docs/ref/models/fields.txt
@@ -173,8 +173,6 @@ If ``True``, djadmin:`django-admin.py sqlindexes <sqlindexes>` will output a
173 173
 
174 174
 .. attribute:: Field.db_tablespace
175 175
 
176  
-.. versionadded:: 1.0
177  
-
178 176
 The name of the database tablespace to use for this field's index, if this field
179 177
 is indexed. The default is the project's :setting:`DEFAULT_INDEX_TABLESPACE`
180 178
 setting, if set, or the :attr:`~Field.db_tablespace` of the model, if any. If
@@ -432,8 +430,6 @@ JavaScript shortcuts.
432 430
 ``DecimalField``
433 431
 ----------------
434 432
 
435  
-.. versionadded:: 1.0
436  
-
437 433
 .. class:: DecimalField(max_digits=None, decimal_places=None, [**options])
438 434
 
439 435
 A fixed-precision decimal number, represented in Python by a
@@ -489,8 +485,6 @@ Has one **required** argument:
489 485
     date/time of the file upload (so that uploaded files don't fill up the given
490 486
     directory).
491 487
 
492  
-    .. versionchanged:: 1.0
493  
-
<