https://github.com/python/cpython/commit/bb007186944f14d7251f97345f18890114babd5f
commit: bb007186944f14d7251f97345f18890114babd5f
branch: 3.13
author: Jost Migenda <[email protected]>
committer: hugovk <[email protected]>
date: 2025-10-07T00:28:57+03:00
summary:

[3.13] gh-118767: remove bool(NotImplemented) from pending-removal document 
(GH-139526) (#139677)

files:
M Doc/deprecations/pending-removal-in-3.14.rst
M Doc/deprecations/pending-removal-in-future.rst

diff --git a/Doc/deprecations/pending-removal-in-3.14.rst 
b/Doc/deprecations/pending-removal-in-3.14.rst
index 0dc4233e926098..e8554a78c608f0 100644
--- a/Doc/deprecations/pending-removal-in-3.14.rst
+++ b/Doc/deprecations/pending-removal-in-3.14.rst
@@ -38,6 +38,10 @@ Pending Removal in Python 3.14
     is no current event loop set and it decides to create one.
     (Contributed by Serhiy Storchaka and Guido van Rossum in :gh:`100160`.)
 
+* :mod:`builtins`: ``bool(NotImplemented)`` now emits a 
:exc:`DeprecationWarning`
+  and will raise a :exc:`TypeError` in Python 3.14.
+  (Contributed by Jelle Zijlstra in :gh:`118767`.)
+
 * :mod:`email`: Deprecated the *isdst* parameter in 
:func:`email.utils.localtime`.
   (Contributed by Alan Williams in :gh:`72346`.)
 
diff --git a/Doc/deprecations/pending-removal-in-future.rst 
b/Doc/deprecations/pending-removal-in-future.rst
index a865e6ce585df3..20707c644e2ac1 100644
--- a/Doc/deprecations/pending-removal-in-future.rst
+++ b/Doc/deprecations/pending-removal-in-future.rst
@@ -9,7 +9,6 @@ although there is currently no date scheduled for their removal.
 
 * :mod:`builtins`:
 
-  * ``bool(NotImplemented)``.
   * Generators: ``throw(type, exc, tb)`` and ``athrow(type, exc, tb)``
     signature is deprecated: use ``throw(exc)`` and ``athrow(exc)`` instead,
     the single argument signature.

_______________________________________________
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]

Reply via email to