Added information to the ticket http://trac.sagemath.org/sage_trac/ticket/9003
Kwankyu Lee
--
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:/
On May 25, 8:39 am, leif wrote:
> On 25 Mai, 14:01, Kwankyu Lee wrote:
>
> > This doctest failure did not occur without applying my own patch, so I
> > thought my patch was the cause. A weird bug indeed...
>
> Interesting. Is this behavior reproducable (i.e. present in all test
> runs)?
Yes, p
On 25 Mai, 14:01, Kwankyu Lee wrote:
> This doctest failure did not occur without applying my own patch, so I
> thought my patch was the cause. A weird bug indeed...
Interesting. Is this behavior reproducable (i.e. present in all test
runs)?
Is your patch on trac? This could help narrowing the o
Hi Leif,
This doctest failure did not occur without applying my own patch, so I
thought my patch was the cause. A weird bug indeed...
Thank you for the pointers.
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sa
On 25 Mai, 11:41, leif wrote:
> This is a known issue, and most probably ;-) not related to your
> patch:
>
> See e.g.http://groups.google.com/group/sage-release/msg/dac6cb862ecf6a8e
Direct link to the ticket:
http://trac.sagemath.org/sage_trac/ticket/9003
-Leif
--
To post to this group, send
On 25 Mai, 11:30, Kwankyu Lee wrote:
> Hi,
>
> I am debugging a patch of my own. Perhaps due to the patch, I get the
> following strange doctest failure.
>
> sage -t "4.4.2/devel/sage-main/sage/modules/free_module.py"
> **
> File
