Sun Jun 30 21:23:11 CDT 2013
So what is the workaround for PuDB?
On Sun, Jun 30, 2013 at 9:21 PM, Fernando Perez <firstname.lastname@example.org> wrote:
> Indeed, way back when IPython made blunt assumptions about being more
> or less in control of the user session, and created lots of global
> state. That made sense when it was only an interactive user shell, but
> now that it's a service to manage namespaces, its core should be much
> more constrained in how it pollutes global structures.
> Unfortunately as Thomas said, cleaning this up takes time and isn't at
> the top of the priority list.
> On Sun, Jun 30, 2013 at 8:31 AM, Thomas Kluyver <email@example.com> wrote:
>> Various parts of the IPython machinery assume that there's only one instance
>> in a given process, and would break with multiple IPython shells in a single
>> process. We're slowly moving away from that, but it's not high priority for
>> On 30 June 2013 05:52, Aaron Meurer <firstname.lastname@example.org> wrote:
>>> In IPython dev, if you try to start an IPython instance from within an
>>> IPython instance, it raises MultipleInstanceError. What is the purpose
>>> of this? It breaks a use-case of mine, which is to start PuDB from
>>> within IPython, then to open the IPython interpreter from within PuDB
>>> while debugging? Is the new way to do things to somehow reattach to
>>> the same IPython instance?
>>> I've CCd the PuDB list.
>>> Aaron Meurer
>>> IPython-dev mailing list
>> IPython-dev mailing list
> Fernando Perez (@fperez_org; http://fperez.org)
> fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
> fernando.perez-at-berkeley: contact me here for any direct mail
> IPython-dev mailing list
More information about the IPython-dev