➜

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 NeilGirdhar
Recipients Alex-Blade, NeilGirdhar
Date 2022-02-13.01:50:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAA68w_mQ_kX-oVdHRedRfzuD=2Lew1Nrb2Sx8ZWCqaK5x2nDcg@mail.gmail.com>
In-reply-to <1644716239.68.0.488332543701.issue46730@roundup.psfhosted.org>
Content 
Thank you, this would have saved me a lot of time!

On Sat, Feb 12, 2022 at 8:37 PM Alexander <report@bugs.python.org> wrote:

>
> Alexander <lakeevveekal@gmail.com> added the comment:
>
> 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?
>
> ----------
> nosy: +Alex-Blade
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue46730>
> _______________________________________
>
History
Date User Action Args
2022-02-13 01:50:38NeilGirdharsetrecipients: + NeilGirdhar, Alex-Blade
2022-02-13 01:50:38NeilGirdharlinkissue46730 messages
2022-02-13 01:50:38NeilGirdharcreate