Please see more on the ticket. It's much more than "few rough edges", it's
code that can easily go into an infinite loop...
Dima
--
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 m
Hi Dima,
Thanks! This was a student project from just about a year ago, so I'm not
surprised that a few rough edges slipped through my first-looks and the reviewers.
Patch looks good. I'll work it up officially tonight, or very soon.
Rob
On 09/01/2011 09:35 AM, Dima Pasechnik wrote:
Hi Ro
Hi Rob,
Please see #11772
Cheers,
Dima
--
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.
On Aug 31, 12:05 am, Dima Pasechnik wrote:
> On a second thought, I just fix the error message, make it less cryptic, by
> throwing an exception explicitly.
I don't see a ticket yet - please cc me when you make one. The
"second thought" sounds like a good improvement.
Rob
--
To post to this g
On a second thought, I just fix the error message, make it less cryptic, by
throwing an exception explicitly.
Sorry for noise.
--
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
