I've slowly been working through what it'll take to get debugging going in JupyterLab. I had a face to face conversation with Brian a while ago where we outlined a broad plan on what this could look like. A quick summary is that was that we'd adapt the VS code protocol to run over Jupyter's shell + iopub channels.
As I've been digging into it I've come up with two big decision points where this starts to break down: Debugging files - https://github.com/jupyter/debugger/issues/8 There's not necessary a Jupyter kernel involved here, and there's plenty of languages which already support this protocol unmodified. Event loops and threads - https://github.com/jupyter/debugger/issues/9 ipykernel is currently structured in such a way that while code is executing the event loop isn't running. I don't think these are strictly blockers to the approach that we've outlined, but issue #9 in particular would require some decent sized changes to ipykernel to do code execution on a different thread than the event loop. Anyway, Fernando suggested that I bring the issues to the group for those who aren't tracking the debugger repo, and I'm extremely open to input on what people view the best solution is :) -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/aa2c967a-3772-4eaa-80bf-6ec017578c47%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
