You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the output only displays after the entire notebook evaluates. However, you may have some computationally expensive cells. From a UI/UX perspective, it would be helpful to see the results get stream as they are available
The text was updated successfully, but these errors were encountered:
Mercury is using execnb for executing cells code. The execnb is waiting for final cell response. We collect all cell's responses and then convert them to HTML with nbconvert Python API.
For sure it can be done in the different way, for example communicate with Python kernel directly, using ZeroMQ and rendering HTML directly in the frontend based on responses from kernel. But right now I don't have time to dig into it.
For me priorities are:
Make framework simple to use.
Make it simple to deploy (and share notebooks with non-technical users).
Make framework fast.
Maybe the easiest way to implement streams might be to look how to capture streams in execnb, and then find a way to construct HTML for single cell.
Currently, the output only displays after the entire notebook evaluates. However, you may have some computationally expensive cells. From a UI/UX perspective, it would be helpful to see the results get stream as they are available
The text was updated successfully, but these errors were encountered: