diff -r 774367d21bf3 Doc/library/array.rst --- a/Doc/library/array.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/array.rst Mon May 16 23:33:40 2016 +0300 @@ -91,7 +91,7 @@ Array objects support the ordinary seque concatenation, and multiplication. When using slice assignment, the assigned value must be an array object with the same type code; in all other cases, :exc:`TypeError` is raised. Array objects also implement the buffer interface, -and may be used wherever :term:`bytes-like object`\ s are supported. +and may be used wherever :term:`bytes-like objects ` are supported. The following data items and methods are also supported: diff -r 774367d21bf3 Doc/library/asyncore.rst --- a/Doc/library/asyncore.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/asyncore.rst Mon May 16 23:33:40 2016 +0300 @@ -100,8 +100,8 @@ any that have been added to the map duri During asynchronous processing, each mapped channel's :meth:`readable` and :meth:`writable` methods are used to determine whether the channel's socket - should be added to the list of channels :c:func:`select`\ ed or - :c:func:`poll`\ ed for read and write events. + should be added to the list of channels :func:`selected ` or + :func:`polled ` for read and write events. Thus, the set of channel events is larger than the basic socket events. The full set of methods that can be overridden in your subclass follows: diff -r 774367d21bf3 Doc/library/audioop.rst --- a/Doc/library/audioop.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/audioop.rst Mon May 16 23:33:40 2016 +0300 @@ -7,7 +7,7 @@ The :mod:`audioop` module contains some useful operations on sound fragments. It operates on sound fragments consisting of signed integer samples 8, 16, 24 -or 32 bits wide, stored in :term:`bytes-like object`\ s. All scalar items are +or 32 bits wide, stored in :term:`bytes-like objects `. All scalar items are integers, unless specified otherwise. .. versionchanged:: 3.4 diff -r 774367d21bf3 Doc/library/base64.rst --- a/Doc/library/base64.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/base64.rst Mon May 16 23:33:40 2016 +0300 @@ -40,7 +40,7 @@ package instead. the modern interface. .. versionchanged:: 3.4 - Any :term:`bytes-like object`\ s are now accepted by all + Any :term:`bytes-like objects ` are now accepted by all encoding and decoding functions in this module. Ascii85/Base85 support added. The modern interface provides: diff -r 774367d21bf3 Doc/library/binascii.rst --- a/Doc/library/binascii.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/binascii.rst Mon May 16 23:33:40 2016 +0300 @@ -21,7 +21,7 @@ higher-level modules. .. note:: ``a2b_*`` functions accept Unicode strings containing only ASCII characters. - Other functions only accept :term:`bytes-like object`\ s (such as + Other functions only accept :term:`bytes-like objects ` (such as :class:`bytes`, :class:`bytearray` and other objects that support the buffer protocol). diff -r 774367d21bf3 Doc/library/email.headerregistry.rst --- a/Doc/library/email.headerregistry.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/email.headerregistry.rst Mon May 16 23:33:40 2016 +0300 @@ -211,7 +211,7 @@ headers. The ``decoded`` value of the header will have all encoded words decoded to unicode. :class:`~encodings.idna` encoded domain names are also decoded to unicode. The - ``decoded`` value is set by :attr:`~str.join`\ ing the :class:`str` value of + ``decoded`` value is set by :attr:`joining ` the :class:`str` value of the elements of the ``groups`` attribute with ``', '``. A list of :class:`.Address` and :class:`.Group` objects in any combination diff -r 774367d21bf3 Doc/library/hashlib.rst --- a/Doc/library/hashlib.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/hashlib.rst Mon May 16 23:33:40 2016 +0300 @@ -41,7 +41,7 @@ Hash algorithms There is one constructor method named for each type of :dfn:`hash`. All return a hash object with the same simple interface. For example: use :func:`sha1` to create a SHA1 hash object. You can now feed this object with :term:`bytes-like -object`\ s (normally :class:`bytes`) using the :meth:`update` method. +objects ` (normally :class:`bytes`) using the :meth:`update` method. At any point you can ask it for the :dfn:`digest` of the concatenation of the data fed to it so far using the :meth:`digest` or :meth:`hexdigest` methods. diff -r 774367d21bf3 Doc/library/logging.config.rst --- a/Doc/library/logging.config.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/logging.config.rst Mon May 16 23:33:40 2016 +0300 @@ -647,7 +647,7 @@ root logger section is given below. :: The ``level`` entry can be one of ``DEBUG, INFO, WARNING, ERROR, CRITICAL`` or ``NOTSET``. For the root logger only, ``NOTSET`` means that all messages will be -logged. Level values are :func:`eval`\ uated in the context of the ``logging`` +logged. Level values are :func:`evaluated ` in the context of the ``logging`` package's namespace. The ``handlers`` entry is a comma-separated list of handler names, which must @@ -691,7 +691,7 @@ handler. If blank, a default formatter ( If a name is specified, it must appear in the ``[formatters]`` section and have a corresponding section in the configuration file. -The ``args`` entry, when :func:`eval`\ uated in the context of the ``logging`` +The ``args`` entry, when :func:`evaluated ` in the context of the ``logging`` package's namespace, is the list of arguments to the constructor for the handler class. Refer to the constructors for the relevant handlers, or to the examples below, to see how typical entries are constructed. :: diff -r 774367d21bf3 Doc/library/threading.rst --- a/Doc/library/threading.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/library/threading.rst Mon May 16 23:33:40 2016 +0300 @@ -197,7 +197,7 @@ There is the possibility that "dummy thr thread objects corresponding to "alien threads", which are threads of control started outside the threading module, such as directly from C code. Dummy thread objects have limited functionality; they are always considered alive and -daemonic, and cannot be :meth:`~Thread.join`\ ed. They are never deleted, +daemonic, and cannot be :meth:`joined `. They are never deleted, since it is impossible to detect the termination of alien threads. @@ -269,7 +269,7 @@ since it is impossible to detect the ter When the *timeout* argument is not present or ``None``, the operation will block until the thread terminates. - A thread can be :meth:`~Thread.join`\ ed many times. + A thread can be joined many times. :meth:`~Thread.join` raises a :exc:`RuntimeError` if an attempt is made to join the current thread as that would cause a deadlock. It is also diff -r 774367d21bf3 Doc/whatsnew/3.4.rst --- a/Doc/whatsnew/3.4.rst Mon May 16 22:35:46 2016 +0300 +++ b/Doc/whatsnew/3.4.rst Mon May 16 23:33:40 2016 +0300 @@ -409,7 +409,7 @@ Some smaller changes made to the core Py evaluating has no elements. (Contributed by Julian Berman in :issue:`18111`.) -* Module objects are now :mod:`weakref`'able. +* Module objects are now :mod:`weakly referenceable `. * Module ``__file__`` attributes (and related values) should now always contain absolute paths by default, with the sole exception of @@ -1113,8 +1113,8 @@ with additional speedups by Antoine Pitr mmap ---- -mmap objects can now be :mod:`weakref`\ ed. (Contributed by Valerie Lambert in -:issue:`4885`.) +mmap objects are now :mod:`weakly referenceable `. +(Contributed by Valerie Lambert in :issue:`4885`.) multiprocessing