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 Alex-Blade
Recipients Alex-Blade, NeilGirdhar
Date 2022-02-13.01:37:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644716239.68.0.488332543701.issue46730@roundup.psfhosted.org>
In-reply-to
Content
Indeed, the error message does not help to identify the problem. Moreover, it collides with similar errors in namedtuple and DynamicClassAttribute which may lead to even more confusion.

I made a draft patch that could help with it (https://github.com/Alex-Blade/cpython/commit/06df3a72dfe462c8fe4eac60dce0ef059b1738f8), but I have a concern related to backwards compatibility (that's why no PR). I don't really understand if according to PEP 387 a change in an exception message should be considered compatibility breaking?
History
Date User Action Args
2022-02-13 01:37:19Alex-Bladesetrecipients: + Alex-Blade, NeilGirdhar
2022-02-13 01:37:19Alex-Bladesetmessageid: <1644716239.68.0.488332543701.issue46730@roundup.psfhosted.org>
2022-02-13 01:37:19Alex-Bladelinkissue46730 messages
2022-02-13 01:37:19Alex-Bladecreate