* http.client.HTTP (does not exist in Python 3) → HTTPConnection
* Server (deprecated) → ServerProxy
* Transport.send_request() grew a new “debug” parameter in Python 3 (revision
  a528f7f8f97a)

After 25032ec29315, compile() will raise a ValueError
if source contains null bytes.

Patch by SilentGhost.

importlib.util.LazyLoader.

The class was checking its argument as to whether its implementation
of create_module() came directly from importlib.abc.Loader. The
problem is that the classes coming from imoprtlib.machinery do not
directly inherit from the ABC as they come from _frozen_importlib.
Because the documentation has always said that create_module() was
ignored, the check has simply been removed.

'level' is specified but no __package__.

This brings the function inline with builtins.__import__(). Thanks to
Manuel Jacob for the patch.

* The Windows-specific binary notice was probably a Python 2 thing
* Make it more obvious gettarinfo() is based on stat(), and that non-ordinary
  files may need special care
* The file name must be text; suggest dummy arcname as a workaround
* Indicate TarInfo may be used directly, not just via gettarinfo()

* Add headings for each concrete and mix-in class and list methods and
  attributes under them
* Fix class and method cross references
* Changed RequestHandler to BaseRequestHandler and added class heading
* Pull out Stream/DatagramRequestHandler definitions
* Reordered the request handler setup(), handle(), finish() methods
* Document constructor parameters for the server classes
* Remove version 2.6 not relevant for Python 3 documentation

the same values as open().

Patch by Aviv Palivoda.

Patch from Chi Hsuan Yen.

versions 10.5 or higher.  Original patch by A. Jesse Jiryu Davis.

no ResourceWarning is emitted.

if the stack is too deep.

The original form is incorrect grammar and feels awkward, even though the
meaning is clear.

not have a math vocabulary.

when the iteration is finished, but when it was failed with error.

Based on patch by Guido van Rossum.

Fixed the documented about buffer overflow error for "es#" and "et#" format
units.

* Various sections were pointing to the section on the string.Formatter
  class, when the section on the common format string syntax is probably more
  appropriate
* Fix references to various format() functions and methods
* Nested replacement fields may contain conversions and format specifiers,
  and this is tested; see Issue #19729 for instance

Based on patches by Brian Brazil and Daniel Rocco.