doc: Fix indentation errors/warnings.

Author: QuLogic

docs/changelog.rst

@@ -463,19 +463,19 @@ v0.11.4:
 
 v0.11.3:
   * The ``futurize`` and ``pasteurize`` scripts add an explicit call to
-  ``future.standard_library.install_hooks()`` whenever modules affected by PEP
-  3108 are imported.
+    ``future.standard_library.install_hooks()`` whenever modules affected by
+    PEP 3108 are imported.
 
   * The ``future.builtins.bytes`` constructor now accepts ``frozenset``
-  objects as on Py3.
+    objects as on Py3.
 
 v0.11.2:
   * The ``past.autotranslate`` feature now finds modules to import more
-  robustly and works with Python eggs.
+    robustly and works with Python eggs.
 
 v0.11.1:
   * Update to ``requirements_py26.txt`` for Python 2.6. Small updates to
-  docs and tests.
+    docs and tests.
 
 v0.11:
   * New ``past`` package with ``past.builtins`` and ``past.translation``

docs/roadmap.rst

@@ -5,14 +5,17 @@ futurize script
 ---------------
 
 1. "Safe" mode -- from Py2 to modern Py2 or Py3 to more-compatible Py3
+
    - Split the fixers into two categories: safe and bold
    - Safe is highly unlikely to break existing Py2 or Py3 support. The
      output of this still requires :mod:`future` imports. Examples:
-     - Compatible metaclass syntax on Py3
-     - Explicit inheritance from object on Py3
+
+      - Compatible metaclass syntax on Py3
+      - Explicit inheritance from object on Py3
 
    - Bold might make assumptions about which strings on Py2 should be
      unicode strings and which should be bytestrings.
+
      - We should also build up a database of which standard library
        interfaces on Py2 and Py3 accept unicode strings versus
        byte-strings, which have changed, and which haven't.

docs/why_python3.rst

@@ -19,7 +19,7 @@ Why are Unicode strings better on Python 3?
 -------------------------------------------
 
 - it is not the default string type (you have to prefix the string
-with a u to get Unicode);
+  with a u to get Unicode);
 
 - it is missing some functionality, e.g. casefold;
 
@@ -30,7 +30,7 @@ with a u to get Unicode);
 - narrow builds take up to two times more memory per string as needed;
 
 - worse, narrow builds have very naive (possibly even "broken")
-handling of code points in the Supplementary Multilingual Planes.
+  handling of code points in the Supplementary Multilingual Planes.
 
 The unicode string type in Python 3 is better because:
 
@@ -39,10 +39,10 @@ The unicode string type in Python 3 is better because:
 - it includes more functionality;
 
 - starting in Python 3.3, it gets rid of the distinction between
-narrow and wide builds;
+  narrow and wide builds;
 
 - which reduces the memory overhead of strings by up to a factor
-of four in many cases;
+  of four in many cases;
 
 - and fixes the issue of SMP code points.
 

future/standard_library/__init__.py

@@ -389,7 +389,7 @@ def scrub_py2_sys_modules():
 def scrub_future_sys_modules():
     """
     On Py2 only: Removes any modules such as ``http`` and ``html.parser`` from
-    the ``sys.modules`` cache. Such modules would confuse code such as this:
+    the ``sys.modules`` cache. Such modules would confuse code such as this::
 
         # PyChecker does something like this:
         try:
@@ -399,21 +399,22 @@ def scrub_future_sys_modules():
         finally:
             PY3 = True
 
-    or this:
+    or this::
 
         import urllib       # We want this to pull in only the Py2 module
                             # after scrub_future_sys_modules() has been called
 
-    or this:
+    or this::
 
         # Requests does this in requests/packages/urllib3/connection.py:
         try: # Python 3
             from http.client import HTTPConnection, HTTPException
         except ImportError:
             from httplib import HTTPConnection, HTTPException
 
-    This function removes items matching this spec from sys.modules:
-        key: new_py3_module_name
+    This function removes items matching this spec from sys.modules::
+
+        key:   new_py3_module_name
         value: either future.backports module or py2 module with
                another name
     """
@@ -742,7 +743,9 @@ def from_import(module_name, *symbol_names, **kwargs):
     and this on Py2:
 
         >>> from future.moves.module_name import symbol_names[0], ...
+
     or:
+
         >>> from future.backports.module_name import symbol_names[0], ...
 
     except that it also handles dotted module names such as ``http.client``.

future/types/newrange.py

@@ -28,7 +28,7 @@ class newrange(Sequence):
     """
     Pure-Python backport of Python 3's range object.  See `the CPython
     documentation for details:
-        <http://docs.python.org/py3k/library/functions.html#range>`_
+    <http://docs.python.org/py3k/library/functions.html#range>`_
     """
 
     def __init__(self, *args):

future/utils/__init__.py

@@ -2,32 +2,38 @@
 A selection of cross-compatible functions for Python 2 and 3.
 
 These come from several sources:
-* Jinja2 (BSD licensed: see https://github.com/mitsuhiko/jinja2/blob/master/LICENSE
-* Pandas compatibility module pandas.compat
-* six.py by Benjamin Peterson
-* Django
+
+    * Jinja2 (BSD licensed: see
+      https://github.com/mitsuhiko/jinja2/blob/master/LICENSE)
+    * Pandas compatibility module pandas.compat
+    * six.py by Benjamin Peterson
+    * Django
 
 This exports useful functions for 2/3 compatible code that are not
 builtins on Python 3:
-* bind_method: binds functions to classes
-* ``native_str_to_bytes`` and ``bytes_to_native_str``
-* ``native_str``: always equal to the native platform string object (because
-  this may be shadowed by imports from future.builtins)
-* lists: lrange(), lmap(), lzip(), lfilter()
-* iterable method compatibility: iteritems, iterkeys, itervalues
-  * Uses the original method if available, otherwise uses items, keys, values.
-* types:
-    * text_type: unicode in Python 2, str in Python 3
-    * binary_type: str in Python 2, bythes in Python 3
-    * string_types: basestring in Python 2, str in Python 3
-
-* bchr(c):
-    Take an integer and make a 1-character byte string
-* bord(c)
-    Take the result of indexing on a byte string and make an integer
-* tobytes(s)
-    Take a text string, a byte string, or a sequence of characters taken
-    from a byte string, and make a byte string.
+
+    * bind_method: binds functions to classes
+    * ``native_str_to_bytes`` and ``bytes_to_native_str``
+    * ``native_str``: always equal to the native platform string object (because
+      this may be shadowed by imports from future.builtins)
+    * lists: lrange(), lmap(), lzip(), lfilter()
+    * iterable method compatibility: iteritems, iterkeys, itervalues
+
+        * Uses the original method if available, otherwise uses items, keys, values.
+
+    * types:
+
+        * text_type: unicode in Python 2, str in Python 3
+        * binary_type: str in Python 2, bythes in Python 3
+        * string_types: basestring in Python 2, str in Python 3
+
+    * bchr(c):
+        Take an integer and make a 1-character byte string
+    * bord(c)
+        Take the result of indexing on a byte string and make an integer
+    * tobytes(s)
+        Take a text string, a byte string, or a sequence of characters taken
+        from a byte string, and make a byte string.
 
 This module also defines a simple decorator called
 ``python_2_unicode_compatible`` (from django.utils.encoding) which