[issue27823] Change bare AttributeError messages to be more informative

Anilyka Barry added the comment: I'd forgotten that I did that. Looking back on it, this is indeed not a good change. Since there hasn't been any traction on in for 5 years, I think it's safe to say it's not something people want. -- resolution: -> rejected stage: patch review -> re

[issue27823] Change bare AttributeError messages to be more informative

Irit Katriel added the comment: -1 As Anilyka wrote: "it (AttributeError) doesn't even mean the attribute doesn't exist, as it may". So it's not safe to fill in a missing message based on the assumption that we know what it should be. -- nosy: +iritkatriel

[issue27823] Change bare AttributeError messages to be more informative

Emanuel Barry added the comment: Thanks for your comments Xiang. Yes, it's not equal to #27794, but it's one of the multiple ways to fix it, so I made a new issue about it. The rationale between a bare `raise AttributeError` being changed is the idea that it carries no information, other than

[issue27823] Change bare AttributeError messages to be more informative

Xiang Zhang added the comment: -1. I don't think this is equal to issue27794. I don't hope when I use `raise AttributeError`, Python hides some magic and sets a message I totally don't want. If you do want a good message, why not passing the message when raising? -- __

[issue27823] Change bare AttributeError messages to be more informative

Changes by Xiang Zhang : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue27823] Change bare AttributeError messages to be more informative

New submission from Emanuel Barry: Attached patch changes bare attribute errors to add a useful error message. As such, `raise AttributeError` and `raise AttributeError(None)` (but not `raise AttributeError('')` for example) inside any of the attribute lookup or descriptor methods (__getattrib