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 bar.harel
Recipients avrahami.ben, bar.harel, eric.smith, gvanrossum, python-dev, rhettinger
Date 2020-10-04.16:15:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601828122.22.0.782289334338.issue41905@roundup.psfhosted.org>
In-reply-to
Content
> When instantiation fails, recheck to see the missing abstract methods had been defined?

I've written about it in the python-ideas discussion as well, and completely agree.

There is no other approach that would guarantee correctness across all APIs, both internal and 3rd party. Adding a function to recalculate will require everyone to use it, and worse, know that it even exists.

The overhead should be quite low as this case is probably rare and the recalculation can happen only on failure.

I'm not sure however, what are the implications of changing Py_TPFLAGS_IS_ABSTRACT during type creation.
History
Date User Action Args
2020-10-04 16:15:22bar.harelsetrecipients: + bar.harel, gvanrossum, rhettinger, eric.smith, python-dev, avrahami.ben
2020-10-04 16:15:22bar.harelsetmessageid: <1601828122.22.0.782289334338.issue41905@roundup.psfhosted.org>
2020-10-04 16:15:22bar.harellinkissue41905 messages
2020-10-04 16:15:22bar.harelcreate