Message 325462 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	izbyshev
Recipients	Oren Milman, berker.peksag, izbyshev, mark.dickinson, meador.inge, serhiy.storchaka
Date	2018-09-15.22:53:38
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
What are the drawbacks of moving all code from __init__ to __new__, at least in master branch (3.8)? IMO it's much more robust than playing whack-a-mole both with ref/memleaks caused by repeated calls to __init__ and absence of initialization checks in all methods.

What are the drawbacks of moving all code from __init__ to __new__, at least in master branch (3.8)? IMO it's much more robust than playing whack-a-mole both with ref/memleaks caused by repeated calls to __init__ and absence of initialization checks in all methods.

History
Date	User	Action	Args
2018-09-15 22:53:38	izbyshev	set	recipients: + izbyshev, mark.dickinson, meador.inge, berker.peksag, serhiy.storchaka, Oren Milman
2018-09-15 22:53:38	izbyshev	set	messageid: <[email protected]>
2018-09-15 22:53:38	izbyshev	link	issue31779 messages
2018-09-15 22:53:38	izbyshev	create