Hi all,

IPython is going to be releasing another in their 0.10.x series, which is what we've been running on for a while. They have recently overhauled all the methods of parallelism, as well as their kernel and engine, and I'm really not clear on how this changes the overall architecture of the system. 0MQ is the underlying machinery they now use, and I've played with it and it's definitely as awesome as they say. Unfortunately it's a bit tricky to get installed.

Anyway, the long and the short of it is that IPython is going to be releasing some backwards incompatible changes, which I don't think I can keep up with. The 0.11 series even breaks the "insert_ipython()" function in yt/funcs.py, as well as iyt, by moving names around and shuffling things about. I don't think I can keep up with the changes. Can someone volunteer to step up and see if they can try to make the various IPython-depending yt components work with both the current (i.e., 'stable') and future (i.e., 'completely re-designed for ground-up parallelism on clusters of a nature most of us don't use') IPython branches?

Thanks,

Matt

---------- Forwarded message ---------- From: Fernando Perez fperez.net@gmail.com Date: Fri, Apr 8, 2011 at 3:55 AM Subject: [IPython-dev] Release plans, yet again. And a road to 1.0, believe it or not. To: IPython Development list ipython-dev@scipy.org

I know, everybody laughs when I talk about releases... But for the two of you still listening:

• 0.10.2 will be out asap, literally as soon as I find a block of a few hours free.  I thought I'd have the rc released last week but some family health problems have made the last week very unpleasant for me, and I'm only now getting back on track.  I should be able to cut the 0.10.2 final on Saturday at the latest.

• 0.11: we now have no pending pull requests and just a few critical bugs.  We do need to give some time to shake out in user testing the massive merges of the past few days, today I discussed with Thomas some important things that need to be done to the sqlite history code, and I have a few local things as well, but since all the big stuff is done, we should be looking at pushing 0.11 out the door finally in just a few weeks.  If you have anything on your local trees that you think is in good shape for 0.11, try to make a pull request before too long (though we'll announce the release freeze in advance, we're not quite there yet).

So now is the time to really start playing with master.  Install zeromq/pyzmq 2.1.4 and take it for a spin.  Anything that breaks, let us know by filing a bug report.  If you think we have already a bug but not listed as critical, please let us know and we'll look into raising its priority.  We want to focus on flushing only the critical bugs before cutting out 0.11, so that we can start a quicker release cycle after 0.11.

The plan will be to try and push small releases after 0.11 to the point where we are happy with the API, and then simply start a stabilization series like matplotlib had, 0.99.x, leading to 1.0.  I don't want to make any promises on when 1.0 will be out, but ideally it would be by this summer.  But we'll see, I've broken those enough times that the joke isn't funny anymore.

Many thanks to everyone who has jumped in recently with so much great work to get us to this state. I particularly want to thank Thomas, whose massive clearing job initially really got us 'unstuck' from behind a pile of accumulated pull requests and bugs, and who now has moved into doing brain surgery right at the core, improving some of our most delicate code in really nice ways (the recent AST inputsplitter refactor).

Cheers,

f

IPython-dev mailing list IPython-dev@scipy.org http://mail.scipy.org/mailman/listinfo/ipython-dev