On Wed, Nov 25, 2009 at 7:26 PM, John H Palmieri <jhpalmier...@gmail.com> wrote: > In ring.pyx, there is code like this: > > if proof: > return NotImplementedError > else: > return False > > I would think that the second line should say "raise > NotImplementedError". (Changing it makes some doctests fail, > though.) Is there a good reason for doing "return > NotImplementedError"?
That's *definitely* a bug (almost certainly my fault). No question about it. I made this #7532: http://trac.sagemath.org/sage_trac/ticket/7532 It sounds like you have a fix already, so just let us know when there is a patch up to review. Thanks! William -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
