On Wed, Nov 8, 2017 at 11:09 AM, vitalije <[email protected]> wrote:
> I have just discovered that blocking client can function also in > non-blocking mode. Just adding keyword argument block=False (which default > value is True in BlockingKernelClient) in get_..._msg calls is enough to > exhibit non-blocking functionality. See the implementation of blocking > channels in jupyter_client.blocking.channels. > ​Excellent work. This seems to be a complete prototype of what we need. I agree that there seems to be no need to subclass any jupyter class. In production code, we might want to replace the "while True" loop in execute_one_cell with a callback that is called at idle time. That will allow Leo to continue running without hanging. Leo's BackgroundProcessManager is likely the best place to manage the callback. I'd like to demonstrate this approach soon. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" 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]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
