Permalink
Browse files

Removed versionadded/changed annotations for 1.5

  • Loading branch information...
1 parent 58c6d02 commit 7b69c3e7758770dd632e1754c30714e91868e037 @timgraham timgraham committed Aug 19, 2013
Showing with 65 additions and 400 deletions.
  1. +0 −6 docs/ref/class-based-views/base.txt
  2. +0 −8 docs/ref/class-based-views/generic-date-based.txt
  3. +0 −5 docs/ref/class-based-views/mixins-date-based.txt
  4. +0 −2 docs/ref/class-based-views/mixins-multiple-object.txt
  5. +0 −4 docs/ref/class-based-views/mixins-simple.txt
  6. +0 −8 docs/ref/contrib/admin/index.txt
  7. +0 −2 docs/ref/contrib/auth.txt
  8. +6 −17 docs/ref/contrib/contenttypes.txt
  9. +0 −4 docs/ref/contrib/gis/geoquerysets.txt
  10. +0 −12 docs/ref/contrib/gis/geos.txt
  11. +0 −4 docs/ref/contrib/staticfiles.txt
  12. +0 −4 docs/ref/databases.txt
  13. +0 −12 docs/ref/django-admin.txt
  14. +0 −4 docs/ref/files/file.txt
  15. +0 −5 docs/ref/forms/api.txt
  16. +0 −9 docs/ref/forms/fields.txt
  17. +2 −8 docs/ref/forms/validation.txt
  18. +0 −5 docs/ref/forms/widgets.txt
  19. +0 −11 docs/ref/models/fields.txt
  20. +0 −2 docs/ref/models/instances.txt
  21. +0 −2 docs/ref/models/options.txt
  22. +12 −26 docs/ref/models/querysets.txt
  23. +0 −8 docs/ref/request-response.txt
  24. +8 −18 docs/ref/settings.txt
  25. +1 −12 docs/ref/signals.txt
  26. +6 −17 docs/ref/template-response.txt
  27. +0 −5 docs/ref/templates/api.txt
  28. +2 −12 docs/ref/templates/builtins.txt
  29. +14 −16 docs/ref/unicode.txt
  30. +0 −14 docs/ref/utils.txt
  31. +0 −2 docs/topics/auth/customizing.txt
  32. +4 −10 docs/topics/auth/default.txt
  33. +0 −2 docs/topics/class-based-views/mixins.txt
  34. +0 −5 docs/topics/db/multi-db.txt
  35. +1 −10 docs/topics/db/queries.txt
  36. +0 −5 docs/topics/http/middleware.txt
  37. +1 −9 docs/topics/http/sessions.txt
  38. +0 −9 docs/topics/http/shortcuts.txt
  39. +0 −2 docs/topics/i18n/translation.txt
  40. +0 −7 docs/topics/logging.txt
  41. +4 −10 docs/topics/pagination.txt
  42. +4 −7 docs/topics/serialization.txt
  43. +0 −4 docs/topics/signals.txt
  44. +0 −2 docs/topics/testing/advanced.txt
  45. +0 −54 docs/topics/testing/overview.txt
@@ -104,12 +104,6 @@ TemplateView
Renders a given template, with the context containing parameters captured
in the URL.
- .. versionchanged:: 1.5
-
- The context used to be populated with a ``{{ params }}`` dictionary of
- the parameters captured in the URL. Now those parameters are first-level
- context variables.
-
**Ancestors (MRO)**
This view inherits methods and attributes from the following views:
@@ -138,24 +138,16 @@ YearArchiveView
* ``year``: A :class:`~datetime.date` object
representing the given year.
- .. versionchanged:: 1.5
-
- Previously, this returned a string.
-
* ``next_year``: A :class:`~datetime.date` object
representing the first day of the next year, according to
:attr:`~BaseDateListView.allow_empty` and
:attr:`~DateMixin.allow_future`.
- .. versionadded:: 1.5
-
* ``previous_year``: A :class:`~datetime.date` object
representing the first day of the previous year, according to
:attr:`~BaseDateListView.allow_empty` and
:attr:`~DateMixin.allow_future`.
- .. versionadded:: 1.5
-
**Notes**
* Uses a default ``template_name_suffix`` of ``_archive_year``.
@@ -328,8 +328,3 @@ BaseDateListView
:meth:`~BaseDateListView.get_date_list_period` is used. ``date_type``
and ``ordering`` are simply passed to
:meth:`QuerySet.dates()<django.db.models.query.QuerySet.dates>`.
-
- .. versionchanged:: 1.5
-
- The ``ordering`` parameter was added, and the default order was
- changed to ascending.
@@ -90,8 +90,6 @@ MultipleObjectMixin
.. attribute:: page_kwarg
- .. versionadded:: 1.5
-
A string specifying the name to use for the page parameter.
The view will expect this prameter to be available either as a query
string parameter (via ``request.GET``) or as a kwarg variable specified
@@ -7,8 +7,6 @@ ContextMixin
.. class:: django.views.generic.base.ContextMixin
- .. versionadded:: 1.5
-
**Methods**
.. method:: get_context_data(**kwargs)
@@ -77,8 +75,6 @@ TemplateResponseMixin
.. attribute:: content_type
- .. versionadded:: 1.5
-
The content type to use for the response. ``content_type`` is passed
as a keyword argument to ``response_class``. Default is ``None`` --
meaning that Django uses :setting:`DEFAULT_CONTENT_TYPE`.
@@ -1235,8 +1235,6 @@ templates used by the :class:`ModelAdmin` views:
.. method:: ModelAdmin.get_list_filter(self, request)
- .. versionadded:: 1.5
-
The ``get_list_filter`` method is given the ``HttpRequest`` and is expected
to return the same kind of sequence type as for the
:attr:`~ModelAdmin.list_filter` attribute.
@@ -1251,8 +1249,6 @@ templates used by the :class:`ModelAdmin` views:
.. method:: ModelAdmin.get_inline_instances(self, request, obj=None)
- .. versionadded:: 1.5
-
The ``get_inline_instances`` method is given the ``HttpRequest`` and the
``obj`` being edited (or ``None`` on an add form) and is expected to return
a ``list`` or ``tuple`` of :class:`~django.contrib.admin.InlineModelAdmin`
@@ -1506,10 +1502,6 @@ templates used by the :class:`ModelAdmin` views:
Sends a message to the user using the :mod:`django.contrib.messages`
backend. See the :ref:`custom ModelAdmin example <custom-admin-action>`.
- .. versionchanged:: 1.5
-
- Keyword arguments were added in Django 1.5.
-
Keyword arguments allow you to change the message level, add extra CSS
tags, or fail silently if the ``contrib.messages`` framework is not
installed. These keyword arguments match those for
@@ -389,8 +389,6 @@ can be used for notification when a user logs in or out.
.. function:: user_login_failed
- .. versionadded:: 1.5
-
Sent when the user failed to login successfully
``sender``
@@ -199,14 +199,18 @@ The ``ContentTypeManager``
Takes either a model class or an instance of a model, and returns the
:class:`~django.contrib.contenttypes.models.ContentType` instance
- representing that model.
+ representing that model. ``for_concrete_model=False`` allows fetching
+ the :class:`~django.contrib.contenttypes.models.ContentType` of a proxy
+ model.
.. method:: get_for_models(*models[, for_concrete_models=True])
Takes a variadic number of model classes, and returns a dictionary
mapping the model classes to the
:class:`~django.contrib.contenttypes.models.ContentType` instances
- representing them.
+ representing them. ``for_concrete_models=False`` allows fetching the
+ :class:`~django.contrib.contenttypes.models.ContentType` of proxy
+ models.
.. method:: get_by_natural_key(app_label, model)
@@ -232,21 +236,6 @@ lookup::
.. _generic-relations:
-.. versionadded:: 1.5
-
- Prior to Django 1.5,
- :meth:`~django.contrib.contenttypes.models.ContentTypeManager.get_for_model` and
- :meth:`~django.contrib.contenttypes.models.ContentTypeManager.get_for_models`
- always returned the :class:`~django.contrib.contenttypes.models.ContentType`
- associated with the concrete model of the specified one(s). That means there
- was no way to retrieve the
- :class:`~django.contrib.contenttypes.models.ContentType` of a proxy model
- using those methods. As of Django 1.5 you can now pass a boolean flag –
- ``for_concrete_model`` and ``for_concrete_models`` respectively – to specify
- wether or not you want to retrieve the
- :class:`~django.contrib.contenttypes.models.ContentType` for the concrete or
- direct model.
-
Generic relations
=================
@@ -949,10 +949,6 @@ __ http://geohash.org/
*Availability*: PostGIS, SpatiaLite
-.. versionchanged:: 1.5
-
- ``geojson`` support for Spatialite > 3.0 has been added.
-
Attaches a ``geojson`` attribute to every model in the queryset that contains the
`GeoJSON`__ representation of the geometry.
@@ -276,10 +276,6 @@ that the SRID value is not included in this representation
because it is not a part of the OGC specification (use the
:attr:`GEOSGeometry.hexewkb` property instead).
-.. versionchanged:: 1.5
-
- Prior to Django 1.5, the Z value of the geometry was dropped.
-
.. attribute:: GEOSGeometry.hexewkb
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
as a Python buffer. SRID value is not included, use the
:attr:`GEOSGeometry.ewkb` property instead.
-.. versionchanged:: 1.5
-
- Prior to Django 1.5, the Z value of the geometry was dropped.
-
.. _ewkb:
.. attribute:: GEOSGeometry.ewkb
@@ -426,8 +418,6 @@ geometry that do not make up other.
.. method:: GEOSGeometry.interpolate(distance)
.. method:: GEOSGeometry.interpolate_normalized(distance)
-.. versionadded:: 1.5
-
Given a distance (float), returns the point (or closest point) within the
geometry (:class:`LineString` or :class:`MultiLineString`) at that distance.
The normalized version takes the distance as a float between 0 (origin) and 1
@@ -443,8 +433,6 @@ geometry and other.
.. method:: GEOSGeometry.project(point)
.. method:: GEOSGeometry.project_normalized(point)
-.. versionadded:: 1.5
-
Returns the distance (float) from the origin of the geometry
(:class:`LineString` or :class:`MultiLineString`) to the point projected on the
geometry (that is to a point of the line the closest to the given point).
@@ -255,8 +255,6 @@ CachedStaticFilesStorage
.. method:: file_hash(name, content=None)
- .. versionadded:: 1.5
-
The method that is used when creating the hashed name of a file.
Needs to return a hash for the given file name and content.
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
useful when using a non-local storage backend to deploy files as documented
in :ref:`staticfiles-from-cdn`.
-.. versionadded:: 1.5
-
If you'd like to retrieve a static URL without displaying it, you can use a
slightly different call:
View
@@ -191,10 +191,6 @@ Django supports MySQL 5.0.3 and higher.
`MySQL 5.0`_ adds the ``information_schema`` database, which contains detailed
data on all database schema. Django's ``inspectdb`` feature uses it.
-.. versionchanged:: 1.5
-
- The minimum version requirement of MySQL 5.0.3 was set in Django 1.5.
-
Django expects the database to support Unicode (UTF-8 encoding) and delegates to
it the task of enforcing transactions and referential integrity. It is important
to be aware of the fact that the two latter ones aren't actually enforced by
View
@@ -256,8 +256,6 @@ to flush.
``--no-initial-data``
~~~~~~~~~~~~~~~~~~~~~
-.. versionadded:: 1.5
-
Use ``--no-initial-data`` to avoid loading the initial_data fixture.
@@ -334,8 +332,6 @@ onto which the data will be loaded.
.. django-admin-option:: --ignorenonexistent
-.. versionadded:: 1.5
-
The :djadminopt:`--ignorenonexistent` option can be used to ignore fields that
may have been removed from models since the fixture was originally generated.
@@ -859,10 +855,6 @@ behavior you can use the ``--no-startup`` option. e.g.::
django-admin.py shell --plain --no-startup
-.. versionadded:: 1.5
-
- The ``--interface`` option was added in Django 1.5.
-
.. versionadded:: 1.6
The ``--no-startup`` option was added in Django 1.6.
@@ -1148,8 +1140,6 @@ synchronize.
``--no-initial-data``
~~~~~~~~~~~~~~~~~~~~~
-.. versionadded:: 1.5
-
Use ``--no-initial-data`` to avoid loading the initial_data fixture.
test <app or test identifier>
@@ -1327,8 +1317,6 @@ clearsessions
.. django-admin:: clearsessions
-.. versionadded:: 1.5
-
Can be run as a cron job or directly to clean out expired sessions.
``django.contrib.sitemaps``
View
@@ -100,10 +100,6 @@ The ``ContentFile`` Class
f1 = ContentFile("esta sentencia está en español")
f2 = ContentFile(b"these are bytes")
- .. versionchanged:: 1.5
-
- ContentFile also accepts Unicode strings.
-
.. currentmodule:: django.core.files.images
The ``ImageFile`` Class
View
@@ -211,11 +211,6 @@ only the valid fields::
>>> f.cleaned_data
{'cc_myself': True, 'message': u'Hi there'}
-.. versionchanged:: 1.5
-
-Until Django 1.5, the ``cleaned_data`` attribute wasn't defined at all when
-the ``Form`` didn't validate.
-
``cleaned_data`` will always *only* contain a key for fields defined in the
``Form``, even if you pass extra data when you define the ``Form``. In this
example, we pass a bunch of extra fields to the ``ContactForm`` constructor,
@@ -573,16 +573,12 @@ For each field, we describe the default widget used if you don't specify
.. attribute:: allow_files
- .. versionadded:: 1.5
-
Optional. Either ``True`` or ``False``. Default is ``True``. Specifies
whether files in the specified location should be included. Either this or
:attr:`allow_folders` must be ``True``.
.. attribute:: allow_folders
- .. versionadded:: 1.5
-
Optional. Either ``True`` or ``False``. Default is ``False``. Specifies
whether folders in the specified location should be included. Either this or
:attr:`allow_files` must be ``True``.
@@ -1065,11 +1061,6 @@ objects (in the case of ``ModelMultipleChoiceField``) into the
* Error message keys: ``required``, ``list``, ``invalid_choice``,
``invalid_pk_value``
- .. versionchanged:: 1.5
-
- The empty and normalized values were changed to be consistently
- ``QuerySets`` instead of ``[]`` and ``QuerySet`` respectively.
-
.. versionchanged:: 1.6
The ``invalid_choice`` message may contain ``%(value)s`` and the
@@ -450,11 +450,5 @@ entries in ``_errors``.
Secondly, once we have decided that the combined data in the two fields we are
considering aren't valid, we must remember to remove them from the
-``cleaned_data``.
-
-.. versionchanged:: 1.5
-
- Django used to remove the ``cleaned_data`` attribute entirely if there were
- any errors in the form. Since version 1.5, ``cleaned_data`` is present even if
- the form doesn't validate, but it contains only field values that did
- validate.
+``cleaned_data``. `cleaned_data`` is present even if the form doesn't
+validate, but it contains only field values that did validate.
@@ -525,11 +525,6 @@ Selector and checkbox widgets
A callable that takes the value of the CheckBoxInput and returns
``True`` if the checkbox should be checked for that value.
- .. versionchanged:: 1.5
-
- Exceptions from ``check_test`` used to be silenced by its caller,
- this is no longer the case, they will propagate upwards.
-
``Select``
~~~~~~~~~~
View
@@ -757,21 +757,16 @@ directory on the filesystem. Has three special arguments, of which the first is
.. attribute:: FilePathField.allow_files
- .. versionadded:: 1.5
-
Optional. Either ``True`` or ``False``. Default is ``True``. Specifies
whether files in the specified location should be included. Either this or
:attr:`~FilePathField.allow_folders` must be ``True``.
.. attribute:: FilePathField.allow_folders
- .. versionadded:: 1.5
-
Optional. Either ``True`` or ``False``. Default is ``False``. Specifies
whether folders in the specified location should be included. Either this
or :attr:`~FilePathField.allow_files` must be ``True``.
-
Of course, these arguments can be used together.
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
:attr:`~CharField.max_length` argument. If you don't specify
:attr:`~CharField.max_length`, a default of 200 is used.
-.. versionadded:: 1.5
-
- The current value of the field will be displayed as a clickable link above the
- input widget.
-
-
Relationship fields
===================
Oops, something went wrong.

0 comments on commit 7b69c3e

Please sign in to comment.