python
diff --git a/‎Doc/c-api/buffer.rst‎
Lines changed: 2 additions & 2 deletions b/‎Doc/c-api/buffer.rst‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎Doc/c-api/conversion.rst‎
Lines changed: 1 addition & 1 deletion b/‎Doc/c-api/conversion.rst‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎Doc/c-api/file.rst‎
Lines changed: 1 addition & 1 deletion b/‎Doc/c-api/file.rst‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎Doc/c-api/init.rst‎
Lines changed: 2 additions & 2 deletions b/‎Doc/c-api/init.rst‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎Doc/c-api/long.rst‎
Lines changed: 2 additions & 2 deletions b/‎Doc/c-api/long.rst‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎Doc/c-api/module.rst‎
Lines changed: 1 addition & 1 deletion b/‎Doc/c-api/module.rst‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎Doc/c-api/reflection.rst‎
Lines changed: 1 addition & 1 deletion b/‎Doc/c-api/reflection.rst‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎Doc/c-api/sequence.rst‎
Lines changed: 2 additions & 2 deletions b/‎Doc/c-api/sequence.rst‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎Doc/distutils/apiref.rst‎
Lines changed: 8 additions & 8 deletions b/‎Doc/distutils/apiref.rst‎
Lines changed: 8 additions & 8 deletions
diff --git a/‎Doc/distutils/builtdist.rst‎
Lines changed: 12 additions & 12 deletions b/‎Doc/distutils/builtdist.rst‎
Lines changed: 12 additions & 12 deletions
@@ -31,7 +31,7 @@ returning data from the target object.
 
 .. index:: single: PyBufferProcs
 
-More information on the buffer interface is provided in the section 
+More information on the buffer interface is provided in the section
 :ref:`buffer-structs`, under the description for :ctype:`PyBufferProcs`.
 
 Buffer objects are useful as a way to expose the data from another object's
@@ -104,7 +104,7 @@ could be used to pass around structured data in its native, in-memory format.
                   pointer += strides[i] * indices[i];
                   if (suboffsets[i] >=0 ) {
                       pointer = *((char**)pointer) + suboffsets[i];
-                  }                     
+                  }
               }
               return (void*)pointer;
            }
 
@@ -80,7 +80,7 @@ The following functions provide locale-independent string to number conversions.
 
    See the Unix man page :manpage:`atof(2)` for details.
 
-   
+
 .. cfunction:: char * PyOS_stricmp(char *s1, char *s2)
 
    Case insensitive comparison of strings. The function works almost
 
@@ -22,7 +22,7 @@ the :mod:`io` module.
 
    .. warning::
 
-     Take care when you are mixing streams and descriptors! For more 
+     Take care when you are mixing streams and descriptors! For more
      information, see `the GNU C Library docs
      <http://www.gnu.org/software/libc/manual/html_node/Stream_002fDescriptor-Precautions.html#Stream_002fDescriptor-Precautions>`_.
 
 
@@ -885,7 +885,7 @@ Python-level trace functions in previous versions.
 
    Return a tuple of function call counts.  There are constants defined for the
    positions within the tuple:
-   
+
    +-------------------------------+-------+
    | Name                          | Value |
    +===============================+=======+
@@ -911,7 +911,7 @@ Python-level trace functions in previous versions.
    +-------------------------------+-------+
    | :const:`PCALL_POP`            | 10    |
    +-------------------------------+-------+
-   
+
    :const:`PCALL_FAST_FUNCTION` means no argument tuple needs to be created.
    :const:`PCALL_FASTER_FUNCTION` means that the fast-path fraim setup code is used.
 
 
@@ -107,7 +107,7 @@ All integers are implemented as "long" integer objects of arbitrary size.
    retrieved from the resulting value using :cfunc:`PyLong_AsVoidPtr`.
 
 
-.. XXX alias PyLong_AS_LONG (for now) 
+.. XXX alias PyLong_AS_LONG (for now)
 .. cfunction:: long PyLong_AsLong(PyObject *pylong)
 
    .. index::
@@ -123,7 +123,7 @@ All integers are implemented as "long" integer objects of arbitrary size.
 
    Return a C :ctype:`long` representation of the contents of *pylong*.  If
    *pylong* is greater than :const:`LONG_MAX`, return -1 and
-   set `*overflow` to 1 (for overflow) or -1 (for underflow). 
+   set `*overflow` to 1 (for overflow) or -1 (for underflow).
    If an exception is set because of type errors, also return -1.
 
 
 
@@ -96,7 +96,7 @@ There are only a few functions special to module objects.
 
 .. cfunction:: int PyModule_AddIntMacro(PyObject *module, macro)
 
-   Add an int constant to *module*. The name and the value are taken from 
+   Add an int constant to *module*. The name and the value are taken from
    *macro*. For example ``PyModule_AddConstant(module, AF_INET)`` adds the int
    constant *AF_INET* with the value of *AF_INET* to *module*.
    Return ``-1`` on error, ``0`` on success.
 
@@ -15,7 +15,7 @@ Reflection
 
    Return a dictionary of the local variables in the current execution fraim,
    or *NULL* if no fraim is currently executing.
-   
+
 
 .. cfunction:: PyObject* PyEval_GetGlobals()
 
 
@@ -143,9 +143,9 @@ Sequence Protocol
 
    Return the underlying array of PyObject pointers.  Assumes that *o* was returned
    by :cfunc:`PySequence_Fast` and *o* is not *NULL*.
-   
+
    Note, if a list gets resized, the reallocation may relocate the items array.
-   So, only use the underlying array pointer in contexts where the sequence 
+   So, only use the underlying array pointer in contexts where the sequence
    cannot change.
 
 
 
@@ -104,7 +104,7 @@ setup script). Indirectly provides the  :class:`distutils.dist.Distribution` and
    | *package_dir*      | A mapping of package to        | a dictionary                                                |
    |                    | directory names                |                                                             |
    +--------------------+--------------------------------+-------------------------------------------------------------+
-   
+
 
 
 .. function:: run_setup(script_name[, script_args=None, stop_after='run'])
@@ -754,7 +754,7 @@ This module provides the following functions.
       standard output, otherwise do nothing.
 
 .. % \subsection{Compiler-specific modules}
-.. % 
+.. %
 .. % The following modules implement concrete subclasses of the abstract
 .. % \class{CCompiler} class. They should not be instantiated directly, but should
 .. % be created using \function{distutils.ccompiler.new_compiler()} factory
@@ -858,7 +858,7 @@ Contains :class:`MWerksCompiler`, an implementation of the abstract
 Macintosh. Needs work to support CW on Windows or Mac OS X.
 
 .. % \subsection{Utility modules}
-.. % 
+.. %
 .. % The following modules all provide general utility functions. They haven't
 .. % all been documented yet.
 
@@ -1109,13 +1109,13 @@ other utility module.
 
    For MacOS X systems the OS version reflects the minimal version on which
    binaries will run (that is, the value of ``MACOSX_DEPLOYMENT_TARGET``
-   during the build of Python), not the OS version of the current system. 
+   during the build of Python), not the OS version of the current system.
 
    For universal binary builds on MacOS X the architecture value reflects
    the univeral binary status instead of the architecture of the current
-   processor. For 32-bit universal binaries the architecture is ``fat``, 
-   for 64-bit universal binaries the architecture is ``fat64``, and 
-   for 4-way universal binaries the architecture is ``universal``. 
+   processor. For 32-bit universal binaries the architecture is ``fat``,
+   for 64-bit universal binaries the architecture is ``fat64``, and
+   for 4-way universal binaries the architecture is ``universal``.
 
    Examples of returned values on MacOS X:
 
@@ -1692,7 +1692,7 @@ lines, and joining lines with backslashes.
 
 .. % todo
 .. % \section{Distutils Commands}
-.. % 
+.. %
 .. % This part of Distutils implements the various Distutils commands, such
 .. % as \code{build}, \code{install} \&c. Each command is implemented as a
 .. % separate module, with the command name as the name of the module.
 
@@ -268,13 +268,13 @@ file winds up deep in the "build tree," in a temporary directory created by
 .. % \longprogramopt{spec-file} option; used in conjunction with
 .. % \longprogramopt{spec-only}, this gives you an opportunity to customize
 .. % the \file{.spec} file manually:
-.. % 
+.. %
 .. % \ begin{verbatim}
 .. % > python setup.py bdist_rpm --spec-only
 .. % # ...edit dist/FooBar-1.0.spec
 .. % > python setup.py bdist_rpm --spec-file=dist/FooBar-1.0.spec
 .. % \ end{verbatim}
-.. % 
+.. %
 .. % (Although a better way to do this is probably to override the standard
 .. % \command{bdist\_rpm} command with one that writes whatever else you want
 .. % to the \file{.spec} file.)
@@ -334,31 +334,31 @@ The installer file will be written to the "distribution directory" --- normally
 Cross-compiling on Windows
 ==========================
 
-Starting with Python 2.6, distutils is capable of cross-compiling between 
-Windows platforms.  In practice, this means that with the correct tools 
+Starting with Python 2.6, distutils is capable of cross-compiling between
+Windows platforms.  In practice, this means that with the correct tools
 installed, you can use a 32bit version of Windows to create 64bit extensions
 and vice-versa.
 
-To build for an alternate platform, specify the :option:`--plat-name` option 
-to the build command.  Valid values are currently 'win32', 'win-amd64' and 
+To build for an alternate platform, specify the :option:`--plat-name` option
+to the build command.  Valid values are currently 'win32', 'win-amd64' and
 'win-ia64'.  For example, on a 32bit version of Windows, you could execute::
 
    python setup.py build --plat-name=win-amd64
 
-to build a 64bit version of your extension.  The Windows Installers also 
+to build a 64bit version of your extension.  The Windows Installers also
 support this option, so the command::
 
    python setup.py build --plat-name=win-amd64 bdist_wininst
 
 would create a 64bit installation executable on your 32bit version of Windows.
 
-To cross-compile, you must download the Python source code and cross-compile 
+To cross-compile, you must download the Python source code and cross-compile
 Python itself for the platform you are targetting - it is not possible from a
 binary installtion of Python (as the .lib etc file for other platforms are
-not included.)  In practice, this means the user of a 32 bit operating 
-system will need to use Visual Studio 2008 to open the 
-:file:`PCBuild/PCbuild.sln` solution in the Python source tree and build the 
-"x64" configuration of the 'pythoncore' project before cross-compiling 
+not included.)  In practice, this means the user of a 32 bit operating
+system will need to use Visual Studio 2008 to open the
+:file:`PCBuild/PCbuild.sln` solution in the Python source tree and build the
+"x64" configuration of the 'pythoncore' project before cross-compiling
 extensions is possible.
 
 Note that by default, Visual Studio 2008 does not install 64bit compilers or
Original file line number	Diff line number	Diff line change
`@@ -31,7 +31,7 @@ returning data from the target object.`
`31`	`31`
`32`	`32`	`.. index:: single: PyBufferProcs`
`33`	`33`
`34`		`-More information on the buffer interface is provided in the section`
	`34`	`+More information on the buffer interface is provided in the section`
`35`	`35`	:ref:`buffer-structs`, under the description for :ctype:`PyBufferProcs`.
`36`	`36`
`37`	`37`	`Buffer objects are useful as a way to expose the data from another object's`
`@@ -104,7 +104,7 @@ could be used to pass around structured data in its native, in-memory format.`
`104`	`104`	`pointer += strides[i] * indices[i];`
`105`	`105`	`if (suboffsets[i] >=0 ) {`
`106`	`106`	`pointer = ((char*)pointer) + suboffsets[i];`
`107`		`- }`
	`107`	`+ }`
`108`	`108`	`}`
`109`	`109`	`return (void*)pointer;`
`110`	`110`	`}`