Typos found by codespell

pep-0002.txt

@@ -67,7 +67,7 @@ Maintainer(s)
 All contributions to the standard library need one or more
 maintainers.  This can be an individual, but it is frequently a group
 of people such as the XML- SIG.  Groups may subdivide maintenance
-tasks among themselves.  One ore more maintainers shall be the *head
+tasks among themselves.  One or more maintainers shall be the *head
 maintainer* (usually this is also the main developer).  Head
 maintainers are convenient people the integrators can address if they
 want to resolve specific issues, such as the ones detailed later in

pep-0042.txt

@@ -106,7 +106,7 @@ Standard Library
   handler, it returns "".  It would be better to make it raise an
   exception (corresponding to EINTR) or to restart.  But these
   changes would have to applied to all places that can do blocking
-  interruptable I/O.  So it's a big project.
+  interruptible I/O.  So it's a big project.
 
   https://bugs.python.org/issue210599
 

pep-0101.txt

@@ -534,7 +534,7 @@ the main repo.
   you will now need to manual remove each blurb entry from
   the ``Misc/NEWS.d/next`` directory that was cherry-picked
   into the release you are working on since that blurb entry
-  is now captured in the merged x.y.z.rst fils for the new
+  is now captured in the merged x.y.z.rst file for the new
   release.  Otherwise, the blurb entry will appear twice in
   the `changelog.html` file, once under `Python next` and again
   under `x.y.z`.

pep-0214.txt

@@ -193,7 +193,7 @@ symbol.
   necessary!  Of course you want the file to be an arbitrary
   expression, not just a single word.  (You definitely want to be
   able to write ``print >>sys.stderr``.)  Without the expression the
-  parser would't be able to distinguish where that expression ends
+  parser wouldn't be able to distinguish where that expression ends
   and where the next one begins, e.g.
 
   ::

pep-0252.txt

@@ -623,7 +623,7 @@ this situation substantially.
 
 - Modification for dynamic types: step 1 and 3 look in the
   dictionary of the type and all its base classes (in MRO
-  sequence, or couse).
+  sequence, or course).
 
 
 Discussion

pep-0287.txt

@@ -271,7 +271,7 @@ SText idea, addressing all of the problems listed above.
 Specification
 =============
 
-The specification and user documentaton for reStructuredText is
+The specification and user documentation for reStructuredText is
 quite extensive.  Rather than repeating or summarizing it all
 here, links to the originals are provided.
 

pep-0340.txt

@@ -270,7 +270,7 @@ Alternatives Considered and Rejected
   an entirely different API than the for-loop, to differentiate
   between the two.  A generator would have to be wrapped in a
   decorator to make it support the block API.  IMO this adds more
-  complexity with very little benefit; and we can't relly deny
+  complexity with very little benefit; and we can't really deny
   that the block-statement is conceptually a loop -- it supports
   break and continue, after all.
 

pep-0367.txt

@@ -481,7 +481,7 @@ The proposal adds a dynamic attribute lookup to the super type, which will
 automatically determine the proper class and instance parameters. Each super
 attribute lookup identifies these parameters and performs the super lookup on
 the instance, as the current super implementation does with the explicit
-invokation of a super instance upon a class and instance.
+invocation of a super instance upon a class and instance.
 
 This proposal relies on sys._getframe(), which is not appropriate for anything
 except a prototype implementation.

pep-0372.txt

@@ -249,7 +249,7 @@ What are the trade-offs of the possible underlying data structures?
      the code a little bit more complex.  All of the basic operations are O(1)
      but the constant factor is increased for __setitem__() and __delitem__()
      meaning that every use case will have to pay for this speedup (since all
-     buildup go through __setitem__). Also, the first traveral incurs a
+     buildup go through __setitem__). Also, the first traversal incurs a
      one-time ``O(n log n)`` sorting cost.  The storage costs are double that
      for the sorted-list-of-keys approach.
 

pep-0374.txt

@@ -1443,7 +1443,7 @@ admitted that svn does not serve the needs of non-committers as well
 as a DVCS does. Because svn only provides its features such as version
 control, branching, etc. to people with commit privileges on the
 repository it can be a hindrance for people who lack commit
-privileges. But DVCSs have no such limitiation as anyone can create a
+privileges. But DVCSs have no such limitation as anyone can create a
 local branch of Python and perform their own local commits without the
 burden that comes with cloning the entire svn repository. Allowing
 anyone to have the same workflow as the core developers was the key

pep-0389.txt

@@ -42,7 +42,7 @@ a valuable addition to the Python libraries.
 
 Why aren't getopt and optparse enough?
 ======================================
-One argument against adding argparse is that thare are "already two
+One argument against adding argparse is that there are "already two
 different option parsing modules in the standard library" [9]_. The
 following is a list of features provided by argparse but not present
 in getopt or optparse:

pep-0400.txt

@@ -192,7 +192,7 @@ file-like objects (same API).
 codecs.open() was the only way to open a text file in Unicode mode
 until Python 2.6. Many Python 2 programs uses this function. Removing
 codecs.open() implies more work to port programs from Python 2 to
-Python 3, especially projets using the same code base for the two
+Python 3, especially projects using the same code base for the two
 Python versions (without using 2to3 program).
 
 codecs.open() is kept for backward compatibility with Python 2.
@@ -201,7 +201,7 @@ codecs.open() is kept for backward compatibility with Python 2.
 Deprecate StreamReader and StreamWriter
 '''''''''''''''''''''''''''''''''''''''
 
-Instanciating StreamReader or StreamWriter must emit a DeprecationWarning in
+Instantiating StreamReader or StreamWriter must emit a DeprecationWarning in
 Python 3.3. Defining a subclass doesn't emit a DeprecationWarning.
 
 codecs.open() will be changed to reuse the builtin open() function

pep-0423.txt

@@ -561,7 +561,7 @@ Actions:
 
   * if you use the `default convention
     <#use-standard-pattern-for-community-contributions>`_, then this
-    document should be enough. Don't reapeat it. You may reference
+    document should be enough. Don't repeat it. You may reference
     it.
 
   * else, tell users about custom conventions in project's

pep-0425.txt

@@ -114,7 +114,7 @@ the CPython 3.3 ABI with debugging.
 The CPython stable ABI is `abi3` as in the shared library suffix.
 
 Implementations with a very unstable ABI may use the first 6 bytes (as
-8 base64-encoded characters) of the SHA-256 hash of ther source code
+8 base64-encoded characters) of the SHA-256 hash of their source code
 revision and compiler flags, etc, but will probably not have a great need
 to distribute binary distributions. Each implementation's community may
 decide how to best use the ABI tag.
@@ -226,7 +226,7 @@ What tag do I use if my distribution uses a feature exclusive to the newest vers
 Why isn't there a `.` in the Python version number?
     CPython has lasted 20+ years without a 3-digit major release. This
     should continue for some time.  Other implementations may use _ as
-    a delimeter, since both - and . delimit the surrounding filename.
+    a delimiter, since both - and . delimit the surrounding filename.
 
 Why normalise hyphens and other non-alphanumeric characters to underscores?
     To avoid conflicting with the "." and "-" characters that separate

pep-0439.txt

@@ -17,7 +17,7 @@ Resolution: https://mail.python.org/pipermail/distutils-sig/2013-August/022527.h
 Abstract
 ========
 
-This PEP proposes the inclusion of a pip boostrap executable in the
+This PEP proposes the inclusion of a pip bootstrap executable in the
 Python installation to simplify the use of 3rd-party modules by Python
 users.
 
@@ -91,7 +91,7 @@ and virtualenv.  Once installed, the pip command proceeds as normal. Once the
 bootstrap process is complete the "pip3" command is no longer the bootstrap
 but rather the full pip command.
 
-A boostrap is used in the place of a the full pip code so that we don't have
+A bootstrap is used in the place of a the full pip code so that we don't have
 to bundle pip and also pip is upgradeable outside of the regular Python
 upgrade timeframe and processes.
 
@@ -110,7 +110,7 @@ The bootstrap process will proceed as follows:
    called "pip3".
 2. The user will invoke a pip command, typically "pip3 install
    <package>", for example "pip3 install Django".
-3. The boostrap script will attempt to import the pip implementation.
+3. The bootstrap script will attempt to import the pip implementation.
    If this succeeds, the pip command is processed normally. Stop.
 4. On failing to import the pip implementation the bootstrap notifies
    the user that it needs to "install pip". It will ask the user whether it
@@ -140,11 +140,11 @@ CA certificate check performed. This facility will be present in Python 3.4+
 using Operating System certificates (see PEP XXXX).
 
 Beyond those arguments controlling index location and download
-options, the "pip3" boostrap command may support further standard pip
+options, the "pip3" bootstrap command may support further standard pip
 options for verbosity, quietness and logging.
 
 The "pip3" command will support two new command-line options that are used
-in the boostrapping, and otherwise ignored. They control where the pip
+in the bootstrapping, and otherwise ignored. They control where the pip
 implementation is installed:
 
 ``--bootstrap``

pep-0442.txt

@@ -34,7 +34,7 @@ Reference
 
 Weak reference
     A directional link from an object to another, which doesn't keep
-    alive its target.  This PEP focusses on non-weak references.
+    alive its target.  This PEP focuses on non-weak references.
 
 Reference cycle
     A cyclic subgraph of directional links between objects, which keeps

pep-0447.txt

@@ -40,7 +40,7 @@ to::
 
          return NotFound
 
-The default implemention of ``__getdescriptor__`` looks in the class
+The default implementation of ``__getdescriptor__`` looks in the class
 dictionary::
 
    class type:
@@ -669,7 +669,7 @@ Discussion threads
 * The initial version of the PEP was send with
   Message-ID `<[email protected]>`_
 
-* Further discusion starting at a message with
+* Further discussion starting at a message with
   Message-ID `<[email protected]>`_
 
 * And more discussion starting at message with

pep-0452.txt

@@ -236,7 +236,7 @@ Changes
 * 2001-09-20: Removed ``reset()`` method completely.
 * 2001-09-28: Set ``digest_size`` to ``None`` for variable-size hashes.
 * 2013-08-15: Added ``block_size`` and ``name`` attributes; clarified that
-  'string' actually referes to bytes-like objects.
+  'string' actually refers to bytes-like objects.
 
 
 Acknowledgements

pep-0454.txt

@@ -78,7 +78,7 @@ implemented in the PySizer project in 2005. PySizer was implemented
 differently: the traceback was stored in frame objects and some Python
 types were linked the trace with the name of object type. PySizer patch
 on CPython adds an overhead on performances and memory footprint, even if
-the PySizer was not used. tracemalloc attachs a traceback to the
+the PySizer was not used. tracemalloc attaches a traceback to the
 underlying layer, to memory blocks, and has no overhead when the module
 is not tracing memory allocations.
 
@@ -313,7 +313,7 @@ Snapshot
 
     All inclusive filters are applied at once, a trace is ignored if no
     inclusive filters match it. A trace is ignored if at least one
-    exclusive filter matchs it.
+    exclusive filter matches it.
 
 
 ``load(filename)`` classmethod:
@@ -526,7 +526,7 @@ Prior Work
   <https://pypi.python.org/pypi/meliae>`_:
   Python Memory Usage Analyzer developed by John A Meinel since 2009
 * `gdb-heap <https://fedorahosted.org/gdb-heap/>`_: gdb script written in
-  Python by Dave Malcom (2010-2011) to analyze the usage of the heap memory
+  Python by Dave Malcolm (2010-2011) to analyze the usage of the heap memory
 * `memory_profiler <https://pypi.python.org/pypi/memory_profiler>`_:
   written by Fabian Pedregosa (2011-2013)
 * `caulk <https://github.com/smartfile/caulk/>`_: written by Ben Timby in 2012

pep-0457.txt

@@ -45,7 +45,7 @@ variadic ``*args`` parameter.  However, there is no Python
 syntax to specify accepting a specific number of
 positional-only parameters.  Put another way, there are
 many builtin functions whose signatures are simply not
-expressable with Python syntax.
+expressible with Python syntax.
 
 This PEP proposes a notation for such signatures that could form the
 basis of a backwards-compatible syntax that should permit implementing

pep-0467.txt

@@ -116,7 +116,7 @@ order functions like ``map``.
 
 These new methods intentionally do NOT offer the same level of general integer
 support as the existing ``int.to_bytes`` conversion method, which allows
-arbitrarily large integers to be converted to arbitarily long bytes objects. The
+arbitrarily large integers to be converted to arbitrarily long bytes objects. The
 restriction to only accept positive integers that fit in a single byte means
 that no byte order information is needed, and there is no need to handle
 negative numbers. The documentation of the new methods will refer readers to

pep-0475.txt

@@ -399,7 +399,7 @@ Closed issues:
   <http://bugs.python.org/issue1049450>`_
 * `subprocess: Popen.communicate() doesn't handle EINTR in some cases
   <http://bugs.python.org/issue12493>`_
-* `multiprocessing.util._eintr_retry doen't recalculate timeouts
+* `multiprocessing.util._eintr_retry doesn't recalculate timeouts
   <http://bugs.python.org/issue12338>`_
 * `file readline, readlines & readall methods can lose data on EINTR
   <http://bugs.python.org/issue12268>`_

pep-0485.txt

@@ -115,7 +115,7 @@ However, users may want to compare other numeric types similarly. In
 theory, it should work for any type that supports ``abs()``,
 multiplication, comparisons, and subtraction. However, the implementation
 in the math module is written in C, and thus can not (easily) use python's
-duck typing. Rather, the values passed into the funciton will be converted
+duck typing. Rather, the values passed into the function will be converted
 to the float type before the calculation is performed. Passing in types
 (or values) that cannot be converted to floats will raise an appropriate
 Exception (TypeError, ValueError, or OverflowError).

pep-0490.txt

@@ -168,7 +168,7 @@ exceptions.
 
 The reference cycle can now be fixed with the new
 ``traceback.TracebackException`` object introduced in Python 3.5. It
-stores informations required to format a full textual traceback without
+stores information required to format a full textual traceback without
 storing local variables.
 
 The ``asyncio`` is impacted by the reference cycle issue. This module

pep-0509.txt

@@ -310,7 +310,7 @@ Expose the version at Python level as a read-only __version__ property
 
 The first version of the PEP proposed to expose the dictionary version
 as a read-only ``__version__`` property at Python level, and also to add
-the property to ``collections.UserDict`` (since this type must mimick
+the property to ``collections.UserDict`` (since this type must mimic
 the ``dict`` API).
 
 There are multiple issues:

pep-0510.txt

@@ -250,7 +250,7 @@ function::
                 # use the specialized code
                 return specialized_code
             elif check == 1:
-                # a guard failed temporarely:
+                # a guard failed temporarily:
                 # try the next specialized code
                 index += 1
             else:
@@ -315,7 +315,7 @@ The ``init()`` function initializes a guard:
 The ``check()`` function checks a guard:
 
 * Return ``0`` on success
-* Return ``1`` if the guard failed temporarely
+* Return ``1`` if the guard failed temporarily
 * Return ``2`` if the guard will always fail: the specialized code must
   be removed
 * Raise an exception and return ``-1`` on error

pep-0511.txt

@@ -514,7 +514,7 @@ Output::
 AST transformer
 ---------------
 
-Similary to the bytecode transformer example, the AST transformer also
+Similarly to the bytecode transformer example, the AST transformer also
 replaces all strings with ``"Ni! Ni! Ni!"``::
 
     import ast

pep-0519.txt

@@ -518,7 +518,7 @@ References
 .. [#python-dev-archive] The python-dev mailing list archive
    (https://mail.python.org/pipermail/python-dev/)
 
-.. [#libc-open] ``open()`` documention for the C standard library
+.. [#libc-open] ``open()`` documentation for the C standard library
    (http://www.gnu.org/software/libc/manual/html_node/Opening-and-Closing-Files.html)
 
 .. [#pathlib] The ``pathlib`` module

pep-0523.txt

@@ -245,7 +245,7 @@ It should be mentioned that the Pyston team was consulted on an
 earlier version of this PEP that was more JIT-specific and they were
 not interested in utilizing the changes proposed because they want
 control over memory layout they had no interest in directly supporting
-CPython itself. An informal discusion with a developer on the PyPy
+CPython itself. An informal discussion with a developer on the PyPy
 team led to a similar comment.
 
 Numba [#numba]_, on the other hand, suggested that they would be

pep-0525.txt

@@ -416,7 +416,7 @@ The data flow is defined as follows:
    unwrapped value as an argument.
 
 2. When ``PyAsyncGenASend.throw(*exc)`` is called for the first time,
-   ``*exc`` is throwed into the parent ``agen`` object.
+   ``*exc`` is thrown into the parent ``agen`` object.
 
    Subsequent iterations over the ``PyAsyncGenASend`` objects, push
    ``None`` to ``agen``.

pep-0531.txt

@@ -269,7 +269,7 @@ appropriate operation (e.g. ``math.isnan``, ``cmath.isnan``,
 
 Similarly, it seems reasonable to declare that the other placeholder builtin
 singletons, ``Ellipsis`` and ``NotImplemented``, also qualify as objects that
-represent the absence of data moreso than they represent data.
+represent the absence of data more so than they represent data.
 
 
 Proposed symbolic notation

pep-0554.rst

@@ -844,7 +844,7 @@ API for sharing data
 Subinterpreters are less useful without a mechanism for sharing data
 between them.  Sharing actual Python objects between interpreters,
 however, has enough potential problems that we are avoiding support
-for that here.  Instead, only mimimum set of types will be supported.
+for that here.  Instead, only minimum set of types will be supported.
 Initially this will include ``None``, ``bytes``, ``str``, ``int``,
 and channels.  Further types may be supported later.
 
@@ -956,7 +956,7 @@ The module also provides the following channel-related classes::
 Channel Lifespan
 ----------------
 
-A channel is automatically closed and destoyed once there are no more
+A channel is automatically closed and destroyed once there are no more
 Python objects (e.g. ``RecvChannel`` and ``SendChannel``) referring
 to it.  So it is effectively triggered via garbage-collection of those
 objects..
@@ -1258,7 +1258,7 @@ this can wait.
 Pipes and Queues
 ----------------
 
-With the proposed object passing machanism of "channels", other similar
+With the proposed object passing mechanism of "channels", other similar
 basic types aren't required to achieve the minimal useful functionality
 of subinterpreters.  Such types include pipes (like unbuffered channels,
 but one-to-one) and queues (like channels, but more generic).  See below