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 gvanrossum
Recipients gvanrossum, iritkatriel, petr.viktorin, yselivanov
Date 2022-01-22.20:26:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1642883218.58.0.2525675261.issue46431@roundup.psfhosted.org>
In-reply-to
Content
Is this a matter of adding some documentation showing how it should be done? Even if we don't want to encourage such subclassing, we do have APIs to support it, and I think we ought to show how to do it, given that you have to coordinate a bunch of things.

How feasible is it to improve the error? (If that error is what you always get when __init__ and __new__ don't agree, maybe that could be a separate, more general issue?)
History
Date User Action Args
2022-01-22 20:26:58gvanrossumsetrecipients: + gvanrossum, petr.viktorin, yselivanov, iritkatriel
2022-01-22 20:26:58gvanrossumsetmessageid: <1642883218.58.0.2525675261.issue46431@roundup.psfhosted.org>
2022-01-22 20:26:58gvanrossumlinkissue46431 messages
2022-01-22 20:26:58gvanrossumcreate