bpo-23722: Fix docs for future __classcell__ changes. (GH-6999) (GH-7000)
(cherry picked from commit 8ae8e6af37f29163ee263e293570cb892dc5b5d5)
Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
diff --git a/Doc/reference/datamodel.rst b/Doc/reference/datamodel.rst
index b4a0dbf..cc8dc95 100644
--- a/Doc/reference/datamodel.rst
+++ b/Doc/reference/datamodel.rst
@@ -1968,7 +1968,7 @@
be propagated up to the ``type.__new__`` call in order for the class to be
initialised correctly.
Failing to do so will result in a :exc:`DeprecationWarning` in Python 3.6,
- and a :exc:`RuntimeWarning` in the future.
+ and a :exc:`RuntimeError` in Python 3.8.
When using the default metaclass :class:`type`, or any metaclass that ultimately
calls ``type.__new__``, the following additional customisation steps are
diff --git a/Doc/whatsnew/3.6.rst b/Doc/whatsnew/3.6.rst
index f7fe70f..c4b6395 100644
--- a/Doc/whatsnew/3.6.rst
+++ b/Doc/whatsnew/3.6.rst
@@ -2261,7 +2261,8 @@
direct references from methods to the implicit ``__class__`` closure
variable, the implicit ``__classcell__`` namespace entry must now be passed
up to ``type.__new__`` for initialisation. Failing to do so will result in
- a :exc:`DeprecationWarning` in 3.6 and a :exc:`RuntimeWarning` in the future.
+ a :exc:`DeprecationWarning` in Python 3.6 and a :exc:`RuntimeError` in
+ Python 3.8.
Changes in the C API
--------------------