[IPython-dev] Curses Frontend

Walter Dörwald walter at livinglogic.de
Fri Mar 12 15:29:15 EST 2010

On 12.03.10 20:22, Brian Granger wrote:

> On Tue, Mar 9, 2010 at 2:56 AM, Walter Dörwald <walter at livinglogic.de> wrote:
>> On 08.03.10 21:38, Brian Granger wrote:
>>> Wendell,
>>>> It looks to me like ipipe is on deathrow for IPython 0.11, and in my
>>>> version of 0.11 it crashes occasionally. It has some interesting
>>>> functionality, but if its not going to be part of the main distribution,
>>>> support for it will have to wait. I'm also a very long way from getting
>>>> any sort of curses frontend working, and that's definitely highest
>>>> priority: basic functionality.
>>> Yes, we need to decide what to do with ipipe for 0.11.  My feeling is that
>>> it should be hosted as a separate project (that is why it is in deathrow)
>>> but this has not been discussed.
>> I have no problem with taking ipipe out of the IPython distribution and
>> releasing it as a separate project.
>> We could have a page in the IPython wiki that lists all external IPython
>> extensions.
> Yes, I think this is a good idea.
>>> We are really wanting to keep the core of
>>> IPython as small as possible, as the code base has grown in size far
>>> beyond our development teams abilities to keep up.
>>> Minimally, ipipe needs to be updated to the new APIs, but that
>>> shouldn't be too difficult.
>> Do you have any hints on how that could be done? What ipipe currently
>> uses is the following:
>>    from IPython.utils import generics
>>    generics.result_display.when_type(Display)(display_display)
> Is there a problem with generics?

No, they work without a problem.

> If so it might be related to this:
> https://bugs.launchpad.net/ipython/+bug/527968

I'm not using generics.complete_object.

> It this is a different issue, could you explain further?

You wrote: "Minimally, ipipe needs to be updated to the new APIs", but
generics.result_display() is the only IPython API that ipipe uses, so I
thould I would have to change something.

> [...]


More information about the IPython-dev mailing list