Message 176602 - 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	sbt
Recipients	sbt, serhiy.storchaka, thomas.chiroux
Date	2012-11-29.01:20:30
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1354152030.95.0.117755647555.issue16572@psf.upfronthosting.co.za>
In-reply-to

Content
> But I think the problem remains: do you agree that Classes should include > a super() call in their __init__ ? No, I don't. I think super() is an attractive nuisance which is difficult to use correctly in an __init__() method, except in the trivial case where you only have one (non-mixin) base class. See https://fuhm.net/super-harmful/

> But I think the problem remains: do you agree that Classes should include 
> a super() call in their __init__ ?

No, I don't.

I think super() is an attractive nuisance which is difficult to use correctly in an __init__() method, except in the trivial case where you only have one (non-mixin) base class.

See https://fuhm.net/super-harmful/

History
Date	User	Action	Args
2012-11-29 01:20:31	sbt	set	recipients: + sbt, serhiy.storchaka, thomas.chiroux
2012-11-29 01:20:30	sbt	set	messageid: <1354152030.95.0.117755647555.issue16572@psf.upfronthosting.co.za>
2012-11-29 01:20:30	sbt	link	issue16572 messages
2012-11-29 01:20:30	sbt	create