From 10a122c0d55b01b053126ef3fd4d9e05ab8f2372 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Sat, 19 May 2018 22:47:05 -0700 Subject: [PATCH] bpo-23722: Fix docs for future __classcell__ changes. (GH-6999) (cherry picked from commit 8ae8e6af37f29163ee263e293570cb892dc5b5d5) Co-authored-by: Serhiy Storchaka --- Doc/reference/datamodel.rst | 2 +- Doc/whatsnew/3.6.rst | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/Doc/reference/datamodel.rst b/Doc/reference/datamodel.rst index c08986f6c0..11a5c54696 100644 --- a/Doc/reference/datamodel.rst +++ b/Doc/reference/datamodel.rst @@ -1887,7 +1887,7 @@ current call is identified based on the first argument passed to the method. 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 6ebd0706d0..88146dc7bc 100644 --- a/Doc/whatsnew/3.6.rst +++ b/Doc/whatsnew/3.6.rst @@ -2270,7 +2270,8 @@ Changes in the Python API 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 -------------------- -- 2.40.0