In-process kernel async API

[davidbrochart]

It seems that Spyder uses ipykernel's in-process kernel. As we are doing a major refactor of ipykernel, I was wondering if it's indeed needed in this project. If yes, how would Spyder be impacted if we were to change the API to be async?

[dalthviz]

Hi @davidbrochart thank you for reaching out! Pinging @ccordoba12 and @impact27 (probably they have a better picture of the implications of such a change)

[ccordoba12]

Hey @davidbrochart, thanks for reaching out. We actually don't use the in-process kernel API. The match you found is because we have a copy of the Qtconsole repo here to ease development.

However, there are several users that depend on it to provide a console connected to the same process a PyQt application is running. That's very useful to explore its internals in an interactive way.

[davidbrochart]

Thanks, I'll look into the Qtconsole then.
Out of curiosity, is Spyder an async application?

[impact27]

@davidbrochart Spyder is a qt application so it uses qt eventloops instead of asyncio. The user code is run in spyder-kernels, which is based on ipykernel, and therefore is an async application