Hi,
> 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.
As you suggested in your previous e-mail, there is a last chance that can save
us: what about creating a new exception say MatrixFormatError which inherits
both ArithmeticError and ValueError. It has the advantage of preserving the
backward compatibility, to be explicit, and if needed one can later on issue a
deprecation warning and remove the inheritance from ArithmeticError.
class MatrixFormatError(ArithmeticError, ValueError):
def __init__(self, value):
self.value = value
def __str__(self):
return repr(self.value)+"(Warning: the inheritance of MatrixFormatError
from AritmeticError is deprecated)"
But it's probably not worth it... What do you think ?
Florent
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
