[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Raymond Hettinger added the comment: Thanks everyone. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Raymond Hettinger added the comment: New changeset c841fb9e065c393bba5d5505238f7e286f1dcfc6 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8': bpo-15542: Documentation incorrectly suggests __init__ called after direct __new__ call (GH-15478) (GH-15506)

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Change by miss-islington : -- pull_requests: +15192 pull_request: https://github.com/python/cpython/pull/15506 ___ Python tracker ___

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Raymond Hettinger added the comment: New changeset 6b16d938d6d1ccb443815e20e8812deed274dc09 by Raymond Hettinger (Joannah Nanjekye) in branch 'master': bpo-15542: Documentation incorrectly suggests __init__ called after direct __new__ call (GH-15478)

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Raymond Hettinger added the comment: FWIW, the underlying code for this in Objects/typeobject.c::type_new(). -- assignee: docs@python -> rhettinger nosy: +rhettinger ___ Python tracker

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Joannah Nanjekye added the comment: Since this has taken long on the tracker, I just opened a PR with proposed changes from Aaron. -- nosy: +nanjekyejoannah ___ Python tracker

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Change by Joannah Nanjekye : -- keywords: +patch pull_requests: +15164 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/15478 ___ Python tracker

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Changes by Ankur Ankan ankuran...@gmail.com: -- nosy: +Ankur.Ankan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15542 ___ ___ Python-bugs-list

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

New submission from Aaron Staley: The documentation for __new__ at http://docs.python.org/reference/datamodel.html#object.__new__ is: object.__new__(cls[, ...]) Called to create a new instance of class cls. __new__() is a static method (special-cased so you need not declare it as such) that

[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

Chris Jerdonek added the comment: Whether or not the current language is technically correct, I would support improving its clarity. Would you like to create a formal patch? Also, note that the newest documentation is published here: