Message208201
| Author | skrah |
|---|---|
| Recipients | georg.brandl, larry, mark.dickinson, serhiy.storchaka, skrah |
| Date | 2014-01-15.22:12:20 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <20140115221219.GA26181@sleipnir.bytereef.org> |
| In-reply-to | <1389812380.95.0.952496699363.issue20260@psf.upfronthosting.co.za> |
| Content | |
|---|---|
I think we cannot change PyLong_AsUnsignedLong() without a deprecation period, if at all. That leaves the option of changing the converters. My preference is to raise either OverflowError or ValueError for *both* out-of-range conditions. People may me used to OverflowError by now -- the usage in PyLong_AsUnsignedLong() dates back to very early revisions -- but there are equally good reasons to use ValueError. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-01-15 22:12:20 | skrah | set | recipients: + skrah, georg.brandl, mark.dickinson, larry, serhiy.storchaka |
| 2014-01-15 22:12:20 | skrah | link | issue20260 messages |
| 2014-01-15 22:12:20 | skrah | create | |