> Crap, you're right. It's not the case the ValueError derives from > ArithmeticError. > > Thus, I now change my mind, and think you should *definitely* stick > with ArithmeticError, for backwards compatibility, etc.
So the idea is that until the end of time the 'wrong' exception will be raised to maintain backward compatibility? That seems odd to me. I see that this isn't actually a big deal (raising the 'wrong' exception) but still, I vote for consistency over backward compatibility. Again, it seems a X.0 release might be the right place to change things like that. Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://www.informatik.uni-bremen.de/~malb _jab: [email protected] --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
