From: Fernando Perez <fperez@co...> - 2003-03-17 20:12:55
> Yes, and the details are here:
>>> As far as IPython integration, it seems both projects should work
>>> together to make sure the correct hooks are in the right places. I
>>> don't know enough about how IPython yet to say whether it can be
>>> re-factored in a way that it can "plug-in" to PyCrust either in the real
>>> sense of a plug-in or as a mix-in class or what ever.
I'm already playing with pycrust because I actually need a visual class
browser for a large code I didn't write and which I'm trying to understand.
I'd suggest you download ipython
(http://www-hep.colorado.edu/~fperez/ipython/) and play a bit with it. It
will probably make further discussion and interaction much smoother if we both
familiarize a bit with each other's stuff, and it shouldn't take you more than
a few minutes to get it going.
I think that ipython and pycrust would really complement each other very well,
and that they would make a great shell for scientific computing work. I hope
we can get good work out of this.
> Okay. Once everyone is subscribed to the PyCrust list I can point out
> the current support for alternate interpreters and we can see what
> might need to be added.
>>> I would suggest we subscribe to the PyCrust list and use that for most
>>> of the initial discussion. That will keep it all in one place and easy
>>> to follow.
I'm already subscribed, and I also sent this message to the list to get things
moving there. If others are also subscribed, we can probably continue the
discussion there. I still sent this message with personal copies in case not
all are in.