[IPython-dev] Closing in on 0.11? We need some review/feedback help

Fernando Perez fperez.net at gmail.com
Wed Jan 13 05:19:44 EST 2010

Hi folks,

I've managed to make enough progress on this machinery that I think we
can soon start looking at what's needed to call it 0.11.  But we could
really use some help with review... We're trying to really do a good
job of looking at each other's work, but I'm afraid I've made things a
bit painful for Brian, who lately has taken the brunt of this.  But
reviewing and critiquing each other's work is the best way to improve
the quality of the project, and I really think we have something very
good coming along...

Right now the merge request for my trunk-dev branch:




shows a diff of ~11400 lines, the result of very little sleep in about
12 days.  There's simply no way that anyone can possibly review all
that line by line, but some testing and overall feedback would be very
welcome, from any of you.  Very importantly, our test status is, as
shown in r1322:

As of this revision, we're down to 0 errors on linux and 1 on windows (that
appears twice). The windows error is tracked here:


And I'm pretty sure the windows error will be trivial for Brian to
fix, and it only shows if you have twisted.  I ran the test suite with
only py2.6.4, pyreadline and nose, and got 0 errors on windows.  I
then installed EPD 6 and ran ipython from the source tree, with the
results above.

So we're in pretty good shape tests-wise.   Furthermore, I've
documented the test system, so that from now on we never again have an
excuse not to blanket our code with tests:


In order to make it as easy as possible for anyone interested to test,
in addition to the branch, here are various self-contained downloads,
including a win32 binary (the ones with bzr.r1321 in the title, the
nightlies are from trunk):


At this point, though we do have some regressions and code that hasn't
been ported over, there are enough improvements both user-facing and
structural, that I think we can begin thinking about 0.11.  But for
that, we need some eyes on this recent coding blitz...

Thanks for any feedback!


More information about the IPython-dev mailing list