On Tue, Feb 10, 2009 at 2:06 AM, Martin Albrecht <m...@informatik.uni-bremen.de> wrote: > >> 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?
I don't think ArithmeticError is the wrong exception. It's not really a bad choice. My claim that it was was based on my wrong assumption that ValueError derives from ArithmeticError, a conclusion I came to upon misreading the Python docs. I would be happy with sticking with ArithmeticError. -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
