[Python-Dev] Inconsistent exception for read-only properties? (original) (raw)
Barry Warsaw barry at python.org
Sun Apr 17 21:09:41 CEST 2005
- Previous message: [Python-Dev] Inconsistent exception for read-only properties?
- Next message: [Python-Dev] Inconsistent exception for read-only properties?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, 2005-04-17 at 12:25, Aahz wrote:
Why is changing an exception more acceptable than creating a new one? (I don't have a strong opinion either way, but I'd like some reasoning; Jack's approach at least doesn't break code.) Especially if the new exception isn't "public" (in the builtins with other exceptions).
Adding an exception that we have to live with forever (even if it's localized to this one module) seems like it would fall under the new feature rubric, whereas I think the choice of exception was just a bug. -Barry
-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 307 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/python-dev/attachments/20050417/94ad9087/attachment.pgp
- Previous message: [Python-Dev] Inconsistent exception for read-only properties?
- Next message: [Python-Dev] Inconsistent exception for read-only properties?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]