https://github.com/python/cpython/commit/342c9e028769e000e228332a520ba7f489a0d665
commit: 342c9e028769e000e228332a520ba7f489a0d665
branch: 3.13
author: Miss Islington (bot) <[email protected]>
committer: AA-Turner <[email protected]>
date: 2025-11-29T14:56:41Z
summary:
[3.13] GH-121970: Remove Docutils list monkeypatch (GH-142056) (#142089)
files:
M Doc/howto/functional.rst
M Doc/library/decimal.rst
M Doc/library/ssl.rst
M Doc/tools/extensions/pyspecific.py
M Doc/whatsnew/3.4.rst
diff --git a/Doc/howto/functional.rst b/Doc/howto/functional.rst
index b0b2414a1a02c8..320dcf7eaca113 100644
--- a/Doc/howto/functional.rst
+++ b/Doc/howto/functional.rst
@@ -4,7 +4,7 @@
Functional Programming HOWTO
********************************
-:Author: A. M. Kuchling
+:Author: \A. M. Kuchling
:Release: 0.32
In this document, we'll take a tour of Python's features suitable for
diff --git a/Doc/library/decimal.rst b/Doc/library/decimal.rst
index ea27e80f5050eb..18cd20124fb860 100644
--- a/Doc/library/decimal.rst
+++ b/Doc/library/decimal.rst
@@ -2067,20 +2067,20 @@ to work with the :class:`Decimal` class::
Decimal FAQ
-----------
-Q. It is cumbersome to type ``decimal.Decimal('1234.5')``. Is there a way to
+Q: It is cumbersome to type ``decimal.Decimal('1234.5')``. Is there a way to
minimize typing when using the interactive interpreter?
-A. Some users abbreviate the constructor to just a single letter:
+A: Some users abbreviate the constructor to just a single letter:
>>> D = decimal.Decimal
>>> D('1.23') + D('3.45')
Decimal('4.68')
-Q. In a fixed-point application with two decimal places, some inputs have many
+Q: In a fixed-point application with two decimal places, some inputs have many
places and need to be rounded. Others are not supposed to have excess digits
and need to be validated. What methods should be used?
-A. The :meth:`~Decimal.quantize` method rounds to a fixed number of decimal
places. If
+A: The :meth:`~Decimal.quantize` method rounds to a fixed number of decimal
places. If
the :const:`Inexact` trap is set, it is also useful for validation:
>>> TWOPLACES = Decimal(10) ** -2 # same as Decimal('0.01')
@@ -2098,10 +2098,10 @@ the :const:`Inexact` trap is set, it is also useful for
validation:
...
Inexact: None
-Q. Once I have valid two place inputs, how do I maintain that invariant
+Q: Once I have valid two place inputs, how do I maintain that invariant
throughout an application?
-A. Some operations like addition, subtraction, and multiplication by an integer
+A: Some operations like addition, subtraction, and multiplication by an integer
will automatically preserve fixed point. Others operations, like division and
non-integer multiplication, will change the number of decimal places and need
to
be followed-up with a :meth:`~Decimal.quantize` step:
@@ -2133,21 +2133,21 @@ to handle the :meth:`~Decimal.quantize` step:
>>> div(b, a)
Decimal('0.03')
-Q. There are many ways to express the same value. The numbers ``200``,
+Q: There are many ways to express the same value. The numbers ``200``,
``200.000``, ``2E2``, and ``.02E+4`` all have the same value at
various precisions. Is there a way to transform them to a single recognizable
canonical value?
-A. The :meth:`~Decimal.normalize` method maps all equivalent values to a single
+A: The :meth:`~Decimal.normalize` method maps all equivalent values to a single
representative:
>>> values = map(Decimal, '200 200.000 2E2 .02E+4'.split())
>>> [v.normalize() for v in values]
[Decimal('2E+2'), Decimal('2E+2'), Decimal('2E+2'), Decimal('2E+2')]
-Q. When does rounding occur in a computation?
+Q: When does rounding occur in a computation?
-A. It occurs *after* the computation. The philosophy of the decimal
+A: It occurs *after* the computation. The philosophy of the decimal
specification is that numbers are considered exact and are created
independent of the current context. They can even have greater
precision than current context. Computations process with those
@@ -2165,10 +2165,10 @@ applied to the *result* of the computation::
>>> pi + 0 - Decimal('0.00005'). # Intermediate values are rounded
Decimal('3.1416')
-Q. Some decimal values always print with exponential notation. Is there a way
+Q: Some decimal values always print with exponential notation. Is there a way
to get a non-exponential representation?
-A. For some values, exponential notation is the only way to express the number
+A: For some values, exponential notation is the only way to express the number
of significant places in the coefficient. For example, expressing
``5.0E+3`` as ``5000`` keeps the value constant but cannot show the
original's two-place significance.
@@ -2183,9 +2183,9 @@ value unchanged:
>>> remove_exponent(Decimal('5E+3'))
Decimal('5000')
-Q. Is there a way to convert a regular float to a :class:`Decimal`?
+Q: Is there a way to convert a regular float to a :class:`Decimal`?
-A. Yes, any binary floating-point number can be exactly expressed as a
+A: Yes, any binary floating-point number can be exactly expressed as a
Decimal though an exact conversion may take more precision than intuition would
suggest:
@@ -2194,19 +2194,19 @@ suggest:
>>> Decimal(math.pi)
Decimal('3.141592653589793115997963468544185161590576171875')
-Q. Within a complex calculation, how can I make sure that I haven't gotten a
+Q: Within a complex calculation, how can I make sure that I haven't gotten a
spurious result because of insufficient precision or rounding anomalies.
-A. The decimal module makes it easy to test results. A best practice is to
+A: The decimal module makes it easy to test results. A best practice is to
re-run calculations using greater precision and with various rounding modes.
Widely differing results indicate insufficient precision, rounding mode issues,
ill-conditioned inputs, or a numerically unstable algorithm.
-Q. I noticed that context precision is applied to the results of operations but
+Q: I noticed that context precision is applied to the results of operations but
not to the inputs. Is there anything to watch out for when mixing values of
different precisions?
-A. Yes. The principle is that all values are considered to be exact and so is
+A: Yes. The principle is that all values are considered to be exact and so is
the arithmetic on those values. Only the results are rounded. The advantage
for inputs is that "what you type is what you get". A disadvantage is that the
results can look odd if you forget that the inputs haven't been rounded:
@@ -2234,9 +2234,9 @@ Alternatively, inputs can be rounded upon creation using
the
>>> Context(prec=5, rounding=ROUND_DOWN).create_decimal('1.2345678')
Decimal('1.2345')
-Q. Is the CPython implementation fast for large numbers?
+Q: Is the CPython implementation fast for large numbers?
-A. Yes. In the CPython and PyPy3 implementations, the C/CFFI versions of
+A: Yes. In the CPython and PyPy3 implementations, the C/CFFI versions of
the decimal module integrate the high speed `libmpdec
<https://www.bytereef.org/mpdecimal/doc/libmpdec/index.html>`_ library for
arbitrary precision correctly rounded decimal floating-point arithmetic [#]_.
diff --git a/Doc/library/ssl.rst b/Doc/library/ssl.rst
index 3ecf1ce44625f4..431c2a360ca4fe 100644
--- a/Doc/library/ssl.rst
+++ b/Doc/library/ssl.rst
@@ -2818,16 +2818,16 @@ of TLS/SSL. Some new TLS 1.3 features are not yet
available.
Steve Kent
:rfc:`RFC 4086: Randomness Requirements for Security <4086>`
- Donald E., Jeffrey I. Schiller
+ Donald E. Eastlake, Jeffrey I. Schiller, Steve Crocker
:rfc:`RFC 5280: Internet X.509 Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile <5280>`
- D. Cooper
+ David Cooper et al.
:rfc:`RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
<5246>`
- T. Dierks et. al.
+ Tim Dierks and Eric Rescorla.
:rfc:`RFC 6066: Transport Layer Security (TLS) Extensions <6066>`
- D. Eastlake
+ Donald E. Eastlake
`IANA TLS: Transport Layer Security (TLS) Parameters
<https://www.iana.org/assignments/tls-parameters/tls-parameters.xml>`_
IANA
diff --git a/Doc/tools/extensions/pyspecific.py
b/Doc/tools/extensions/pyspecific.py
index 8fce95f470d37e..20603b6cdd2b70 100644
--- a/Doc/tools/extensions/pyspecific.py
+++ b/Doc/tools/extensions/pyspecific.py
@@ -24,14 +24,6 @@
# Used in conf.py and updated here by python/release-tools/run_release.py
SOURCE_URI = 'https://github.com/python/cpython/tree/3.13/%s'
-# monkey-patch reST parser to disable alphabetic and roman enumerated lists
-from docutils.parsers.rst.states import Body
-Body.enum.converters['loweralpha'] = \
- Body.enum.converters['upperalpha'] = \
- Body.enum.converters['lowerroman'] = \
- Body.enum.converters['upperroman'] = lambda x: None
-
-
class PyAwaitableMixin(object):
def handle_signature(self, sig, signode):
ret = super(PyAwaitableMixin, self).handle_signature(sig, signode)
diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst
index 5ad4f1c4a5e494..a4c6aaa9fa773e 100644
--- a/Doc/whatsnew/3.4.rst
+++ b/Doc/whatsnew/3.4.rst
@@ -2,7 +2,7 @@
What's New In Python 3.4
****************************
-:Author: R. David Murray <[email protected]> (Editor)
+:Author: \R. David Murray <[email protected]> (Editor)
.. Rules for maintenance:
_______________________________________________
Python-checkins mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3//lists/python-checkins.python.org
Member address: [email protected]
