[issue46730] Please consider mentioning property without setter when an attribute can't be set

[Neil Girdhar]

Neil Girdhar <mistersheik at gmail.com> added the comment:

Thank you, this would have saved me a lot of time!

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

>
> Alexander <lakeevveekal at 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 at bugs.python.org>
> <https://bugs.python.org/issue46730>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue46730>
_______________________________________