bpo-23722: Fix docs for future __classcell__ changes. (GH-6999)

This commit is contained in:
Serhiy Storchaka 2018-05-20 08:13:52 +03:00 committed by GitHub
parent 63536bd286
commit 8ae8e6af37
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 2 deletions

View File

@ -1968,7 +1968,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 be propagated up to the ``type.__new__`` call in order for the class to be
initialised correctly. initialised correctly.
Failing to do so will result in a :exc:`DeprecationWarning` in Python 3.6, 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 When using the default metaclass :class:`type`, or any metaclass that ultimately
calls ``type.__new__``, the following additional customisation steps are calls ``type.__new__``, the following additional customisation steps are

View File

@ -2261,7 +2261,8 @@ Changes in the Python API
direct references from methods to the implicit ``__class__`` closure direct references from methods to the implicit ``__class__`` closure
variable, the implicit ``__classcell__`` namespace entry must now be passed variable, the implicit ``__classcell__`` namespace entry must now be passed
up to ``type.__new__`` for initialisation. Failing to do so will result in 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 Changes in the C API
-------------------- --------------------