I have thought a bit more, and it *would* open up using SymPy inside
other applications (GUIs, as part of an array of problem solvers,
whatever). Can't name any concrete killer app, but making a piece of
software more generally useful and seeing what people make of it is
always a good idea.
I'm still very uneasy about adding something to _ask - I may be mistaken
but I think it's part of the "old assumptions system" and on the way
out. Any other part of SymPy would suffer from a similar insecurity,
plus hacking on SymPy would also require knowing about how timeouts are
implemented, contributing to the entry barrier (which isn't *that* high,
but keeping it low requires an active effort).
One alternative approach that I can think about is running SymPy in a
separate process, via Popen. The calling program would be just a stub
that serializes (via pickle) its parameters to the subprocess, sets a
timer, kills the subprocess if it times out, and reads back any results.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sympy.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sympy/544B30B6.1040905%40durchholz.org.
For more options, visit https://groups.google.com/d/optout.
