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 martin.panter
Recipients Gerrit.Holl, docs@python, martin.panter, terry.reedy
Date 2015-10-31.11:40:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If existing subclasses like FileIO call the base, that is an implementation detail. But custom subclasses of the Raw, Buffered, and Text base classes should not be prohibited from chain calling the base’s __init__() method, nor should they have to override __init__() if there is no special initialization to be done. For IOBase itself, I don’t see a strong argument either way, but it makes sense to keep it consistent with the other three base classes.

I propose this patch, which changes “There is no public constructor” to “The constructor accepts no arguments”. In my mind this blesses making custom subclasses, which already seems to be tested and used in practice.
Date User Action Args
2015-10-31 11:40:02martin.pantersetrecipients: + martin.panter, terry.reedy, docs@python, Gerrit.Holl
2015-10-31 11:40:02martin.pantersetmessageid: <>
2015-10-31 11:40:02martin.panterlinkissue25415 messages
2015-10-31 11:40:00martin.pantercreate