traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

bpo-15542: Documentation incorrectly suggests __init__ called after direct __new__ call (GH-15478)

This commit is contained in:
Joannah Nanjekye 2019-08-26 03:53:11 -03:00 committed by Raymond Hettinger
parent 1039f39c9c
commit 6b16d938d6
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Doc/reference/datamodel.rst
View File

@ -1166,10 +1166,10 @@ Basic customization
with appropriate arguments and then modifying the newly-created instance
as necessary before returning it.
If :meth:`__new__` returns an instance of *cls*, then the new instance's
:meth:`__init__` method will be invoked like ``__init__(self[, ...])``, where
*self* is the new instance and the remaining arguments are the same as were
passed to :meth:`__new__`.
If :meth:`__new__` is invoked during object construction and it returns an
instance or subclass of *cls*, then the new instance’s :meth:`__init__` method
will be invoked like ``__init__(self[, ...])``, where *self* is the new instance
and the remaining arguments are the same as were passed to the object constructor.
If :meth:`__new__` does not return an instance of *cls*, then the new instance's
:meth:`__init__` method will not be invoked.