Python 3.4.0rc1 release: Updated pydoc topics, fixed suspicious markup errors.

This commit is contained in:
Larry Hastings 2014-02-10 04:26:10 -08:00
parent 8f9f0f12e8
commit ad88d7a26b
5 changed files with 13 additions and 13 deletions

View File

@ -77,7 +77,7 @@ An event loop policy must implement the following interface:
Create and return a new event loop object according to this policy's rules.
If there's need to set this loop as the event loop of the current context,
:meth`set_event_loop` must be called explicitly.
:meth:`set_event_loop` must be called explicitly.
Access to the global loop policy
--------------------------------

View File

@ -30,7 +30,7 @@ one decorator, :func:`unique`.
.. class:: Enum
Base class for creating enumerated constants. See section
:ref:`Functional API` for an alternate construction syntax.
`Functional API`_ for an alternate construction syntax.
.. class:: IntEnum
@ -421,7 +421,7 @@ The solution is to specify the module name explicitly as follows::
>>> Animals = Enum('Animals', 'ant bee cat dog', module=__name__)
The new pickle protocol 4 also, in some circumstances, relies on
:attr:``__qualname__`` being set to the location where pickle will be able
:attr:`__qualname__` being set to the location where pickle will be able
to find the class. For example, if the class was made available in class
SomeData in the global scope::

View File

@ -1917,13 +1917,13 @@ Loading and running tests
By default this runner shows :exc:`DeprecationWarning`,
:exc:`PendingDeprecationWarning`, :exc:`ResourceWarning` and
:exc:`ImportWarning` even if they are :ref:`ignored by default <warning-
ignored>`. Deprecation warnings caused by :ref:`deprecated unittest methods
<deprecated-aliases>` are also special-cased and, when the warning filters
are ``'default'`` or ``'always'``, they will appear only once per-module, in
order to avoid too many warning messages. This behavior can be overridden
using the :option:`-Wd` or :option:`-Wa` options and leaving *warnings* to
``None``.
:exc:`ImportWarning` even if they are :ref:`ignored by default
<warning-ignored>`. Deprecation warnings caused by :ref:`deprecated unittest
methods <deprecated-aliases>` are also special-cased and, when the warning
filters are ``'default'`` or ``'always'``, they will appear only once
per-module, in order to avoid too many warning messages. This behavior can
be overridden using the :option:`-Wd` or :option:`-Wa` options and leaving
*warnings* to ``None``.
.. versionchanged:: 3.2
Added the ``warnings`` argument.

View File

@ -1708,7 +1708,7 @@ Changes in the Python API
Changes in the C API
--------------------
* :c:func:`PyEval_EvalFrameEx`, :c:func:`PyObject_Repr(), and
* :c:func:`PyEval_EvalFrameEx`, :c:func:`PyObject_Repr`, and
:c:func:`PyObject_Str`, along with some other internal C APIs, now include
a debugging assertion that ensures they are not used in situations where
they may silently discard a currently active exception. In cases where

File diff suppressed because one or more lines are too long