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 ncoghlan
Recipients CuriousLearner, ncoghlan, serhiy.storchaka, xtreak
Date 2018-09-24.12:06:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537790779.49.0.956365154283.issue31506@psf.upfronthosting.co.za>
In-reply-to
Content
We added the method names to help provide a nudge that the issue is likely to be a missing method implementation in the subclassing case, so I'd like to keep them if we can find a way to make the messages accurate again.

What if we updated the offending format strings in typeobject.c to state the exact nature of the expected argument that is missing?

    PyErr_SetString(PyExc_TypeError, "object.__init__() takes exactly one argument (the instance to initialize)");

    PyErr_Format(PyExc_TypeError, "%.200s.__init__() takes exactly one argument (the instance to initialize)", type->tp_name);

    PyErr_SetString(PyExc_TypeError, "object.__new__() takes exactly one argument (the type to instantiate)")
History
Date User Action Args
2018-09-24 12:06:19ncoghlansetrecipients: + ncoghlan, serhiy.storchaka, CuriousLearner, xtreak
2018-09-24 12:06:19ncoghlansetmessageid: <1537790779.49.0.956365154283.issue31506@psf.upfronthosting.co.za>
2018-09-24 12:06:19ncoghlanlinkissue31506 messages
2018-09-24 12:06:19ncoghlancreate