[1.7.x] Fixed versionchanged indentation in docs/.

        available for new content to be written to on the target storage

        system.

        .. versionchanged:: 1.7

        If a file with ``name`` already exists, an underscore plus a random

        7 character alphanumeric string is appended to the filename before

        the extension.

        If a file with ``name`` already exists, an underscore plus a random 7

        character alphanumeric string is appended to the filename before the

        extension.

        .. versionchanged:: 1.7

        Previously, an underscore followed by a number (e.g. ``"_1"``, ``"_2"``,

        etc.) was appended to the filename until an available name in the

        destination directory was found. A malicious user could exploit this

        deterministic algorithm to create a denial-of-service attack. This

        change was also made in Django 1.6.6, 1.5.9, and 1.4.14.

            Previously, an underscore followed by a number (e.g. ``"_1"``,

            ``"_2"``, etc.) was appended to the filename until an available

            name in the destination directory was found. A malicious user could

            exploit this deterministic algorithm to create a denial-of-service

            attack. This change was also made in Django 1.6.6, 1.5.9, and

            1.4.14.

    .. method:: get_valid_name(name)

   >>> without_relations = queryset.select_related(None)

Chaining ``select_related`` calls works in a similar way to other methods -

that is that ``select_related('foo', 'bar')`` is equivalent to

``select_related('foo').select_related('bar')``.

.. versionchanged:: 1.7

Chaining ``select_related`` calls now works in a similar way to other methods -

that is that ``select_related('foo', 'bar')`` is equivalent to

``select_related('foo').select_related('bar')``. Previously the latter would

have been equivalent to ``select_related('bar')``.

    Previously the latter would have been equivalent to

    ``select_related('bar')``.

prefetch_related

~~~~~~~~~~~~~~~~

image in the above example will be 88 pixels wide

(because 175/200 = .875; .875 * 100 = 87.5 which is rounded up to 88).

.. versionchanged:: 1.7

In some cases you might want to capture the result of ``widthratio`` in a

variable. It can be useful, for instance, in a :ttag:`blocktrans` like this::

    {% widthratio this_value max_value max_width as width %}

    {% blocktrans %}The width is: {{ width }}{% endblocktrans %}

.. versionchanged:: 1.7

    The ability to use "as" with this tag like in the example above was added.

.. templatetag:: with

with

.. versionchanged:: 1.7

Before version 1.7, the ``cached_db`` backend always used the ``default`` cache

rather than the :setting:`SESSION_CACHE_ALIAS`.

    Before version 1.7, the ``cached_db`` backend always used the ``default``

    cache rather than the :setting:`SESSION_CACHE_ALIAS`.

Using file-based sessions

-------------------------