Commit 6b16d938 authored by Joannah Nanjekye's avatar Joannah Nanjekye Committed by Raymond Hettinger

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

parent 1039f39c
...@@ -1166,10 +1166,10 @@ Basic customization ...@@ -1166,10 +1166,10 @@ Basic customization
with appropriate arguments and then modifying the newly-created instance with appropriate arguments and then modifying the newly-created instance
as necessary before returning it. as necessary before returning it.
If :meth:`__new__` returns an instance of *cls*, then the new instance's If :meth:`__new__` is invoked during object construction and it returns an
:meth:`__init__` method will be invoked like ``__init__(self[, ...])``, where instance or subclass of *cls*, then the new instance’s :meth:`__init__` method
*self* is the new instance and the remaining arguments are the same as were will be invoked like ``__init__(self[, ...])``, where *self* is the new instance
passed to :meth:`__new__`. 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 If :meth:`__new__` does not return an instance of *cls*, then the new instance's
:meth:`__init__` method will not be invoked. :meth:`__init__` method will not be invoked.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment