Hey Brian, I think all the issues I've come across are ones I've told you about. To recap
1. Add capability so multiple groups of engines and remote controllers can operate on one machine without conflicting. 2. Keep track of the worker and controllers (PID)/clean up spawned processes gracefully. 3. Ability to toggle off special ipython output. 4. Ability to specify controller imports. Josh On Feb 15, 10:54 pm, "Brian Granger" <[EMAIL PROTECTED]> wrote: > Hello SAGE folks, > > I wanted to update all of you on the status of IPython1 - aka chainsaw... > > I am giving a talk about IPython at PyCon next week. In preparation > for this, and in preparation of SAGE days 3, we are getting a new > release of the parallel stuff ready. This release will be called > "saw." rather than chainsaw. We have been working on the saw branch > for two months now and there are massive improvements over the > chainsaw version. More details on this next week. > > I am emailing all of you because I wanted to see if there was anything > specific you would like to see go into this release that is > missing/broken in chainsaw. Over the last week or so we have > interacted with a number of you about a few issues. Most of those > things have already been addressed. Anyway, please let us know if > there are things you want to see done by the end of next week. > > We really do want feedback about this stuff. > > Thanks > > Brian --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
