[IPython-dev] [IPython-user] IPython development news and prospects

Ville M. Vainio vivainio at gmail.com
Sun Jan 13 18:11:58 EST 2008

On Jan 14, 2008 12:06 AM, Fernando Perez <fperez.net at gmail.com> wrote:

> My proposal is very simple: we go with hg.  Other related projects to


> - Next comes documentation.  I'll work on transferring the manual over
> to a bunch of reST files, so we can have reST based manual(s).  After
> we do this, we will hopefully start doing a very, very good job of
> always documenting things correctly in the reST sources, rather than
> having the hodgepodge of outdated manual + random wiki pages we have
> today.

Great, I'm quite willing to update the manual with more current
information when this happens.

> - Configuration: for this, we've more or less decided to just going
> with TConfig:
> http://projects.scipy.org/ipython/ipython/browser/ipython1/trunk/sandbox/tconfig
> The only downside tconfig has is a dependence on Enthought Traits,
> which has C code.  The upsides are vast, including a *clean* way of

As long as the C code is not shipped with IPython and the binaries are
readily available, no problem.

> What I'd like to know is if Ville and the others who have a stake on
> trunk are willing to basically join in together, starting mid to late
> March, on this effort.  My idea is that we'll eventually have ALL the

Obviously I can't make any kind of formal commitment, but I will
certainly be kicking the tires of the new codebase.

Porting over existing trunk code is something that I can see myself
doing, at least.

> But there will be enough work to be done here, and it touches on what
> all have contributed so much, that I want to find the best way to
> manage a transition so that:
> - nobody feels like their work is dropped/ignored

I don't see the current trunk going away any day soon, even if we some
day decide to call it "ready" :-)

Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'

More information about the IPython-dev mailing list