Message 284637 - 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	jdemeyer
Recipients	Ringding, Trundle, aronacher, benjamin.peterson, doko, jdemeyer, larry, ned.deily, prologic, python-dev, scoder, sebastinas, serhiy.storchaka, thansen, vstinner
Date	2017-01-04.14:04:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1483538663.43.0.00363349700947.issue5322@psf.upfronthosting.co.za>
In-reply-to

Content
It worries me that nothing in the Python docs nor in any PEP describes how tp_new is inherited. In my opinion, this patch makes a significant change which should be subject to a PEP. However, neither the old nor new behaviour is described anywhere. This also makes it harder to argue which behaviour is correct.

It worries me that nothing in the Python docs nor in any PEP describes how tp_new is inherited. In my opinion, this patch makes a significant change which should be subject to a PEP. However, neither the old nor new behaviour is described anywhere. This also makes it harder to argue which behaviour is correct.

History
Date	User	Action	Args
2017-01-04 14:04:23	jdemeyer	set	recipients: + jdemeyer, doko, scoder, vstinner, larry, sebastinas, benjamin.peterson, ned.deily, aronacher, prologic, Trundle, Ringding, python-dev, serhiy.storchaka, thansen
2017-01-04 14:04:23	jdemeyer	set	messageid: <1483538663.43.0.00363349700947.issue5322@psf.upfronthosting.co.za>
2017-01-04 14:04:23	jdemeyer	link	issue5322 messages
2017-01-04 14:04:23	jdemeyer	create