[IPython-dev] IPEP 7: Notebook dependent frontends
Fri Nov 23 18:20:48 CST 2012
I don't disagree that we want IPython to be useful as a library, I
just didn't think that is what this IPEP was going to be about
On Wed, Nov 21, 2012 at 11:21 AM, Carl Smith <firstname.lastname@example.org> wrote:
>> Wouldn't it be better to add some kind of "rejected" status to the IPEP,
>> similar to regular Python PEPs? In fact, I find the status part of regular
>> PEPs to be the most useful part, because it's otherwise not clear if the PEP
>> was already implemented, or being implemented, or still being
>> written/discussed, or rejected, or what.
> This sounds like a good idea in general, though I do still think this
> IPEP is worth considering.
> The Notebook currently imposes a number of major limitations that
> inhibit development by third parties. There's growing, and already
> significant, interest in using the IPython Notebook in ways that
> IPython Dev are unlikely to work on directly. I think it's important
> to have IPython work well as a library for reuse, and this IPEP at
> least opens up exploration of how that can be achieved on one
> important front, web clients.
> IPython-dev mailing list
Brian E. Granger
Cal Poly State University, San Luis Obispo
email@example.com and firstname.lastname@example.org
More information about the IPython-dev