Message241033
| Author | blackfawn |
|---|---|
| Recipients | BreamoreBoy, barry, blackfawn, brett.cannon, cvrebert, ezio.melotti |
| Date | 2015-04-14.21:29:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1429046959.9.0.654088320705.issue18166@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
So, this is actually impossible to do. Since exceptions are c-level classes, adding members to ValueError means anything that multiple-inherits from ValueError and any other complex exception gets a multiple bases layout conflict. There's already one such class - _pyio.UnsupportedOperation inherits both ValueError and OSError - but the bigger issue is that this would break compatibility. After discussing it (face-to-face) with a bunch of core devs, I think the only reasonable course of action is to close the issue and never speak of this again. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-04-14 21:29:19 | blackfawn | set | recipients: + blackfawn, barry, brett.cannon, ezio.melotti, cvrebert, BreamoreBoy |
| 2015-04-14 21:29:19 | blackfawn | set | messageid: <1429046959.9.0.654088320705.issue18166@psf.upfronthosting.co.za> |
| 2015-04-14 21:29:19 | blackfawn | link | issue18166 messages |
| 2015-04-14 21:29:19 | blackfawn | create | |