Message215877
| Author |
skrah |
| Recipients |
garybernhardt, gdr@garethrees.org, josh.r, mark.dickinson, ncoghlan, pitrou, skrah, vstinner |
| Date |
2014年04月10日.13:08:56 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<20140410130856.GA24363@sleipnir.bytereef.org> |
| In-reply-to |
<1397133125.77.0.221203522984.issue20539@psf.upfronthosting.co.za> |
| Content |
Mark Dickinson <report@bugs.python.org> wrote:
> > the whole idea of OverflowError seems slightly outdated.
>
> Well, not entirely. It's still got a place for overflow of mathematical operations, and I think it's clearly the correct exception in that case (indeed, it's about the only case I can think of where OverflowError is clearly the correct exception).
Indeed, I was focusing on integer arithmetic and assignments. For float
operations and conversions OverflowError is quite natural.
> (3) Given the lack of clarity about which exception types are appropriate where, I think we shouldn't be changing exception types unless/until there's a clear vision of where we want to end up. Getting that clear vision may require a python-dev discussion.
Using OverflowError for now sounds like a good plan. |
|