Thomas Kluyver

Was this actually fixed? I think there was still a problem related to the Qt event loop after #141 landed.

(I don't think it's strictly a Qt console problem - it's more likely to be something in the kernel - but I want to work this out properly before closing)

This is not. If we're aiming to get 4.2 out soon, it's fine to bump this.

OK. I've created a new 4.3 milestone and set it to that, on the grounds that it does still make sense to add API docs for a minor release if...

`IPython.embed()` is expecting to run terminal IPython, so I'm not surprised that running it inside an IPython kernel connected to a frontend goes very wrong. I'd be inclined to say...

It may be more likely to work if you use `embed_kernel()`. You may then need to connect another client to it, I'm not sure.

Please try to describe what you're seeing in more detail than "these do not work".

Thanks. cc @minrk - is there any chance that could be an issue with the io-capturing machinery in the kernel? I remember it involves a fair bit of complexity now....

Check other environment variables besides PATH. Also check `sys.executable` in Python to ensure that you're using the same Python installation in the terminal and in the Qt console.

> if there is a way to get the actual output to go into the split pager I don't think there's a way to send output there directly, but `IPython.core.page.page()`...