Removed versionadded/changed annotations for 1.5

    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:

    * ``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``.

        :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.

    .. 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

.. class:: django.views.generic.base.ContextMixin

    .. versionadded:: 1.5

    **Methods**

    .. method:: get_context_data(**kwargs)

    .. 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`.