Remove trailing spaces. (#232)

Changes made automatically by the following command:
```
egrep -l ' +$' *.txt | xargs sed -i -re 's/ +$//'
```

Author: serhiy-storchaka

pep-0005.txt

@@ -77,7 +77,7 @@ Steps For Introducing Backwards-Incompatible Features
    deprecated construct to the alternative one.
 
 ..
-   Local Variables: 
-   mode: indented-text 
-   indent-tabs-mode: nil 
+   Local Variables:
+   mode: indented-text
+   indent-tabs-mode: nil
    End:

pep-0012.txt

@@ -267,7 +267,7 @@ per indent level.
 Literal Blocks
 --------------
 
-..  
+..
     In the text below, double backquotes are used to denote inline
     literals.  "``::``" is written so that the colons will appear in a
     monospaced font; the backquotes (``) are markup, not part of the

pep-0100.txt

@@ -195,7 +195,7 @@ Unicode Ordinals
                   objects)
         --> Unicode ordinal number (32-bit)
 
-      unichr(i) 
+      unichr(i)
           --> Unicode object for character i (provided it is 32-bit);
               ValueError otherwise
 
@@ -277,7 +277,7 @@ Codecs (Coder/Decoders) Lookup
     following arguments:
 
       encoder and decoder:
-      
+
         These must be functions or methods which have the same
         interface as the .encode/.decode methods of Codec instances
         (see Codec Interface). The functions/methods are expected to
@@ -413,7 +413,7 @@ Codecs Interface Definition
                Use StreamCodec for codecs which have to keep state in
                order to make encoding/decoding efficient.
 
-            """ 
+            """
 
     StreamWriter and StreamReader define the interface for stateful
     encoders/decoders which work on streams.  These allow processing
@@ -626,7 +626,7 @@ Case Conversion
     Case conversion is rather complicated with Unicode data, since
     there are many different conditions to respect.  See
 
-      http://www.unicode.org/unicode/reports/tr13/ 
+      http://www.unicode.org/unicode/reports/tr13/
 
     for some guidelines on implementing case conversion.
 
@@ -725,11 +725,11 @@ Internal Format
     additional constants for convenience and reference (codecs.BOM
     will either be BOM_BE or BOM_LE depending on the platform):
 
-      BOM_BE: '\376\377' 
+      BOM_BE: '\376\377'
         (corresponds to Unicode U+0000FEFF in UTF-16 on big endian
          platforms == ZERO WIDTH NO-BREAK SPACE)
 
-      BOM_LE: '\377\376' 
+      BOM_LE: '\377\376'
         (corresponds to Unicode U+0000FFFE in UTF-16 on little endian
          platforms == defined as being an illegal Unicode character)
 
@@ -841,7 +841,7 @@ Internal Argument Parsing
 
       "t#": Same as "s#".
 
-      "es": 
+      "es":
             Takes two parameters: encoding (const char *) and buffer
             (char **).
 
@@ -902,7 +902,7 @@ Internal Argument Parsing
             return str;
         }
 
-    Using "es" with auto-allocation returning a NULL-terminated string:    
+    Using "es" with auto-allocation returning a NULL-terminated string:
 
         static PyObject *
         test_parser(PyObject *self,
@@ -978,7 +978,7 @@ Unicode Methods & Attributes
 
     All Python string methods, plus:
 
-      .encode([encoding=<default encoding>][,errors="strict"]) 
+      .encode([encoding=<default encoding>][,errors="strict"])
          --> see Unicode Output
 
       .splitlines([include_breaks=0])

pep-0101.txt

@@ -180,7 +180,7 @@ How to Make A Release
 
   ___ Commit your changes to pydoc_topics.py
       (and any fixes you made in the docs).
- 
+
   ___ Consider running autoconf using the currently accepted standard version
       in case ``configure`` or other autoconf-generated files were last
       committed with a newer or older version and may contain spurious or
@@ -464,7 +464,7 @@ How to Make A Release
 
           You should always purge the cache of the directory listing as people
           use that to browse the release files:
-          
+
           $ curl -X PURGE https://www.python.org/ftp/python/2.7.5/
 
   ___ For the extra paranoid, do a completely clean test of the release.
@@ -561,17 +561,17 @@ How to Make A Release
       are removed, too.)
 
   ___ If this is a final release...
-  
+
       ___ Add the new version to `https://www.python.org/doc/versions/` and
           remove the current version from any 'in development' section.
 
       ___ For X.Y.Z, edit all the previous X.Y releases' page(s) to
           point to the new release.  This includes the content field of the
           `Downloads -> Releases` entry for the release::
-          
+
             Note: Python x.y.m has been superseded by
             `Python x.y.n </downloads/release/python-xyn/>`_.
-          
+
           And, for those releases having separate release page entries
           (phasing these out?), update those pages as well,
           e.g. `download/releases/x.y.z::

pep-0102.txt

@@ -2,8 +2,8 @@ PEP: 102
 Title: Doing Python Micro Releases
 Version: $Revision$
 Last-Modified: $Date$
-Author: [email protected] (Anthony Baxter), 
-    [email protected] (Barry Warsaw), 
+Author: [email protected] (Anthony Baxter),
+    [email protected] (Barry Warsaw),
     [email protected] (Guido van Rossum)
 Status: Superseded
 Type: Informational
@@ -34,7 +34,7 @@ Abstract
     is just PEP 101, trimmed down to only include the bits that are
     relevant for micro releases, a.k.a. patch, or bug fix releases.
 
-    It is organized as a recipe and you can actually print this out and 
+    It is organized as a recipe and you can actually print this out and
     check items off as you complete them.
 
 
@@ -61,11 +61,11 @@ How to Make A Release
     maintenance branch of the major release, e.g. Python 2.1.2 is made
     from the release21-maint branch.
 
-  ___ Send an email to [email protected] indicating the release is 
+  ___ Send an email to [email protected] indicating the release is
       about to start.
 
-  ___ Put a freeze on check ins into the maintenance branch.  At this 
-      point, nobody except the RM should make any commits to the branch 
+  ___ Put a freeze on check ins into the maintenance branch.  At this
+      point, nobody except the RM should make any commits to the branch
       (or his duly assigned agents, i.e. Guido the BDFL, Fred Drake for
       documentation, or Thomas Heller for Windows).  If the RM screwed up
       and some desperate last minute change to the branch is
@@ -189,8 +189,8 @@ How to Make A Release
       merging Windows-specific changes from trunk to branch, and from
       branch to trunk.
 
-  ___ Sean performs his Red Hat magic, generating a set of RPMs.  He 
-      uploads these files to python.org.  He then sends the RM a notice 
+  ___ Sean performs his Red Hat magic, generating a set of RPMs.  He
+      uploads these files to python.org.  He then sends the RM a notice
       which includes the location and MD5 checksum of the RPMs.
 
   ___ It's Build Time!
@@ -231,7 +231,7 @@ How to Make A Release
       % tar -cf - Python-2.1.2 | gzip -9 > Python-2.1.2.tgz
       % tar -cf - Python-2.1.2 | bzip2 -9 > Python-2.1.2.tar.bz2
 
-  ___ Calculate the MD5 checksum of the tgz and tar.bz2 files you 
+  ___ Calculate the MD5 checksum of the tgz and tar.bz2 files you
       just created
       % md5sum Python-2.1.2.tgz
 
@@ -434,17 +434,17 @@ Final Release Notes
         lose patience <wink>.
 
     The python.org site also needs some tweaking when a new bugfix release
-    is issued.  
+    is issued.
 
     ___ The documentation should be installed at doc/<version>/.
 
-    ___ Add a link from doc/<previous-minor-release>/index.ht to the 
+    ___ Add a link from doc/<previous-minor-release>/index.ht to the
         documentation for the new version.
 
-    ___ All older doc/<old-release>/index.ht files should be updated to 
+    ___ All older doc/<old-release>/index.ht files should be updated to
         point to the documentation for the new version.
 
-    ___ /robots.txt should be modified to prevent the old version's 
+    ___ /robots.txt should be modified to prevent the old version's
         documentation from being crawled by search engines.
 
 

pep-0200.txt

@@ -27,7 +27,7 @@ Release Schedule
 [revised 5 Oct 2000]
 
 
-* 26-Sep-2000: 2.0 beta 2 
+* 26-Sep-2000: 2.0 beta 2
 * 9-Oct-2000: 2.0 release candidate 1 (2.0c1)
 * 16-Oct-2000: 2.0 final
 
@@ -366,7 +366,7 @@ Postponed
 
   - http://www.python.org/pipermail/python-dev/2000-April/subject.html
     Subject: "Why do we need Traceback Objects?"
-  
+
   - http://www.python.org/pipermail/python-dev/1999-August/002252.html
 
 * test harness for C code - Trent Mick

pep-0201.txt

@@ -54,7 +54,7 @@ in function::
     >>> a = (1, 2, 3)
     >>> b = (4, 5, 6)
     >>> for i in map(None, a, b): print i
-    ... 
+    ...
     (1, 4)
     (2, 5)
     (3, 6)
@@ -83,7 +83,7 @@ For these reasons, several proposals were floated in the Python 2.0
 beta time frame for syntactic support of lockstep for-loops. Here are
 two suggestions::
 
-  for x in seq1, y in seq2: 
+  for x in seq1, y in seq2:
     # stuff
 
 ::

pep-0202.txt

@@ -24,7 +24,7 @@ The Proposed Solution
 It is proposed to allow conditional construction of list literals using for and
 if clauses.  They would nest in the same way for loops and if statements nest
 now.
-    
+
 
 Rationale
 =========