The testing framework automatically runs set_random_seed(0) before
testing every docstring, so this shouldn't be necessary.
Carl Witty
OK.
Setting the random seed seems like a fine workaround for getting your
patch in... the problem is unlikely to be in your patch, as you point
out.
But as the author of both sage.misc.randstate and
sage.symbolic.random_tests, it makes me nervous when I don't
understand what my code is doing. I tried to look into this, but I
couldn't figure out how to reproduce the problem. Could you do me a
favor and give nice simple instructions? (In particular, what version
of Sage do I start with and what is the complete list of patches to
apply?)
Thanks,
Carl
Thanks, that's exactly what I needed to track down the issue. Turns
out it was a bug in random_tests.py. (I was inadvertently depending
on the order of the output of .values() on a dict, which is a Bad
Idea. The question isn't why it broke, it's why did it ever work.)
There's a patch up at #9514.
Carl
Andrey
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>