Comment #32 on issue 1026 by [email protected]: pypy doesn't run sympy http://code.google.com/p/sympy/issues/detail?id=1026
Well, we also can't really ask people to test in PyPy if we have a lot of (known) errors; we should fix them first. I wouldn't mind doing this, as I said I will, but the test runner not crashing is an important prerequisite. I don't know how to do this, though, do you have any ideas? Is this an upstream bug? (something about failing gracefully like it used to)
But yes, I also agree that if we make it faster in PyPy people will naturally come. I'm not sure what will be needed to do this, but the first order of business is to make some actual benchmarks. Care needs to be given to this and I'm not really familiar with SymPy internals enough to do this (I don't even use SymPy normally!); perhaps we could ask the others on the list? (I consider benchmarks a separate issue, of course) Once we have some speed measurements, we can focus on speeding up SymPy (both in PyPy and CPython 2, 3); I also think most speed improvements could happen upstream, if only we can demonstrate them clearly. The PyPy developers also have an interest in running SymPy (and fast) so I don't see why they wouldn't help too.
-- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy-issues?hl=en.
