With this seed, the process hangs. While doing that, it uses up a lot
of memory. It's hard for me to reproduce exactly, because Mac OS X
apparently will gladly give Python as much memory as it wants,
including virtual memory, until my hard disk fills up.
We really need to figure out why this is
> Did you clip the output, or did it really jump to utilities here?
I didn't include all the output, but what I did include is contiguous.
It was at utilities at that point in the run.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this gr
On Jul 12, 2012, at 9:04 PM, smichr wrote:
Is something wrong with the bot test(s)? Notice how part way into a test
run it looks like the run starts over again:
running test
= test process starts ==
executable: /usr/bin/python2.7 (
Is something wrong with the bot test(s)? Notice how part way into a test
run it looks like the run starts over again:
running test
= test process starts ==
executable: /usr/bin/python2.7 (2.7.3-candidate-2)
architecture: 64-bi
