rewrap

Author: methane

Doc/library/ctypes.rst

@@ -3759,9 +3759,8 @@ fields, or any other data types containing pointer type fields.
    :module: ctypes.util
 
    Information regarding a structure field defined by the
-   :func:`~ctypes.util.struct`
-   decorator. This should be used in the second argument of a
-   :class:`typing.Annotated` wrapping a ctypes type.
+   :func:`~ctypes.util.struct` decorator. This should be used in the second
+   argument of a :class:`typing.Annotated` wrapping a ctypes type.
 
    *anonymous* specifies whether the field will be present in the
    :attr:`~ctypes.Structure._anonymous_` attribute of the generated class.

Doc/library/datetime.rst

@@ -1387,9 +1387,8 @@ Instance methods:
    tzinfo=self.tzinfo, *, fold=0)
 
    Return a new :class:`~datetime.datetime` object with the same attributes, but
-   with
-   specified parameters updated. Note that ``tzinfo=None`` can be specified to
-   create a naive datetime from an aware datetime with no conversion of date
+   with specified parameters updated. Note that ``tzinfo=None`` can be specified
+   to create a naive datetime from an aware datetime with no conversion of date
    and time data.
 
    :class:`.datetime` objects are also supported by generic function

Doc/library/getopt.rst

@@ -81,11 +81,9 @@ exception:
 .. function:: gnu_getopt(args, shortopts, longopts=[])
 
    This function works like :func:`~getopt.getopt`, except that GNU style
-   scanning mode is
-   used by default. This means that option and non-option arguments may be
-   intermixed. The :func:`~getopt.getopt` function stops processing options as
-   soon as a
-   non-option argument is encountered.
+   scanning mode is used by default. This means that option and non-option
+   arguments may be intermixed. The :func:`~getopt.getopt` function stops
+   processing options as soon as a non-option argument is encountered.
 
    If the first character of the option string is ``'+'``, or if the environment
    variable :envvar:`!POSIXLY_CORRECT` is set, then option processing stops as

Doc/library/getpass.rst

@@ -28,14 +28,13 @@ The :mod:`!getpass` module provides two functions:
    display asterisks instead of the actual input.
 
    If echo-free input is unavailable, :func:`~getpass.getpass` falls back to
-   printing
-   a warning message to *stream* and reading from :data:`sys.stdin` and
+   printing a warning message to *stream* and reading from :data:`sys.stdin` and
    issuing a :exc:`GetPassWarning`.
 
    .. note::
       If you call :func:`~getpass.getpass` from within IDLE, the input may be
-      done in the
-      terminal you launched IDLE from rather than the idle window itself.
+      done in the terminal you launched IDLE from rather than the idle window
+      itself.
 
    .. note::
       On Unix systems, when *echo_char* is set, the terminal will be

Doc/library/gettext.rst

@@ -90,8 +90,8 @@ class-based API instead.
 
    Similar to the corresponding functions without the ``p`` in the prefix (that
    is, :func:`~gettext.gettext`, :func:`dgettext`, :func:`ngettext`,
-   :func:`dngettext`),
-   but the translation is restricted to the given message *context*.
+   :func:`dngettext`), but the translation is restricted to the given message
+   *context*.
 
    .. versionadded:: 3.8
 

Doc/library/marshal.rst

@@ -59,8 +59,7 @@ this module.  The following types are supported:
   Recursive containers are supported since :data:`version` 3.
 * The singletons :const:`None`, :const:`Ellipsis` and :exc:`StopIteration`.
 * :class:`code <types.CodeType>` objects, if *allow_code* is true. See note
-  above about
-  version dependence.
+  above about version dependence.
 
 .. versionchanged:: 3.4
 

Doc/library/mmap.rst

@@ -426,11 +426,10 @@ PROT_* constants
           PROT_EXEC
 
    Memory protection flags accepted by the *prot* argument of
-   :class:`~mmap.mmap`.
-   :const:`PROT_READ` allows pages to be read, :const:`PROT_WRITE` allows pages
-   to be written, and :const:`PROT_EXEC` allows pages to be executed. Values
-   can be combined using the bitwise OR operator. Not every option is present
-   on every system.
+   :class:`~mmap.mmap`. :const:`PROT_READ` allows pages to be read,
+   :const:`PROT_WRITE` allows pages to be written, and :const:`PROT_EXEC` allows
+   pages to be executed. Values can be combined using the bitwise OR operator.
+   Not every option is present on every system.
 
    .. availability:: Unix.
 

Doc/library/multiprocessing.rst

@@ -2463,10 +2463,10 @@ with the :class:`Pool` class.
 
    .. warning::
       :class:`~multiprocessing.pool.Pool` objects have internal resources that
-      need to be
-      properly managed (like any other resource) by using the pool as a context manager
-      or by calling :meth:`close` and :meth:`terminate` manually. Failure to do this
-      can lead to the process hanging on finalization.
+      need to be properly managed (like any other resource) by using the pool as
+      a context manager or by calling :meth:`close` and :meth:`terminate`
+      manually. Failure to do this can lead to the process hanging on
+      finalization.
 
       Note that it is **not correct** to rely on the garbage collector to destroy the pool
       as CPython does not assure that the finalizer of the pool will be called

Doc/library/multiprocessing.shared_memory.rst

@@ -223,9 +223,9 @@ same :class:`!numpy.ndarray` from two distinct Python shells:
 
    This class provides methods for creating and returning
    :class:`~multiprocessing.shared_memory.SharedMemory` instances and for
-   creating
-   a list-like object (:class:`~multiprocessing.shared_memory.ShareableList`)
-   backed by shared memory.
+   creating a list-like object
+   (:class:`~multiprocessing.shared_memory.ShareableList`) backed by shared
+   memory.
 
    Refer to :class:`~multiprocessing.managers.BaseManager` for a description
    of the inherited *address* and *authkey* optional input arguments and how
@@ -235,14 +235,14 @@ same :class:`!numpy.ndarray` from two distinct Python shells:
    .. method:: SharedMemory(size)
 
       Create and return a new
-      :class:`~multiprocessing.shared_memory.SharedMemory`
-      object with the specified *size* in bytes.
+      :class:`~multiprocessing.shared_memory.SharedMemory` object with the
+      specified *size* in bytes.
 
    .. method:: ShareableList(sequence)
 
       Create and return a new
-      :class:`~multiprocessing.shared_memory.ShareableList`
-      object, initialized by the values from the input *sequence*.
+      :class:`~multiprocessing.shared_memory.ShareableList` object, initialized
+      by the values from the input *sequence*.
 
 
 The following example demonstrates the basic mechanisms of a

Doc/library/optparse.rst

@@ -2041,10 +2041,9 @@ Finally, the Option subclass::
        TYPE_CHECKER["complex"] = check_complex
 
 (If we didn't make a :func:`~copy.copy` of :attr:`Option.TYPE_CHECKER`, we would
-end
-up modifying the :attr:`~Option.TYPE_CHECKER` attribute of :mod:`!optparse`'s
-Option class.  This being Python, nothing stops you from doing that except good
-manners and common sense.)
+end up modifying the :attr:`~Option.TYPE_CHECKER` attribute of
+:mod:`!optparse`'s Option class.  This being Python, nothing stops you from
+doing that except good manners and common sense.)
 
 That's it!  Now you can write a script that uses the new option type just like
 any other :mod:`!optparse`\ -based script, except you have to instruct your