On Mar 19, 9:09 am, Ondrej Certik <ond...@certik.cz> wrote: > On Thu, Mar 19, 2009 at 12:56 AM, Ondrej Certik <ond...@certik.cz> wrote: > > [...] > > > I forgot to ask the question: > > > how could this be made more efficient using some native ipython parrallel > > tools? > > And last question: > > Currently all the engines must be able to import sympy and I noticed > it is not even enough to install sympy after each change, but the > ipcluster must be restarted as well, otherwise the old version of > sympy stays in the memory and it fails. > > What is the best way to transfer the library (sympy) and tests to the > engines automatically to make the edit/run/debug cycle easier? > > And what about a big cluster --- wouldn't it be handy to just tell > ipython: take this library and make it available on the engines, > without me requiring to install it manually and then restarting the > ipcluster?
You can tell Python to import/reload a module using an explicit path, for example: module = __import__(name) So ideally you only pass the path to the engines. Vinzent --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
