[IPython-dev] strange namespace issue

Fernando Perez fperez.net at gmail.com
Mon Sep 10 14:35:56 EDT 2007

On 9/10/07, Darren Dale <dd55 at cornell.edu> wrote:

> I can't spend any more time on this now. If I knew how to solve this problem,
> we could run pyqt* programs in ipython, they would be non-blocking, and it
> would be possible to inspect the application state. Instead, I'm leaving it
> so the programs do block, this way they run without errors.

No worries.  It's still worth noting that *some* Qt4 apps can be run
in non-blocking mode as you state.

Try grabbing the demo3_qt4 file from here:


as well as wiggly.py and dutil.py.

Then do:

ipython -q4thread dutil.py


%rundemo demo3_qt4.py



That should give you a live qt4 app that you can interactively
control, while the terminal is responsive.

Keep on typing


to run the demo to completion.

Just a data point, I don't really know what's different in this simple
little demo compared to the more complicated ones.  It just shows that
in *some* cases it works.  It'd be nice to know what's going on so we
could make it work in all cases.



More information about the IPython-dev mailing list