Feature/execute ipython

[ChengJiale150]

See in #89

[ChengJiale150]

Currently, it's implemented by adding a temporary Code Cell at the end of the Notebook, executing it to get the output, and then deleting it. This is not elegant, and it will be improved in the future

[echarles]

Currently, it's implemented by adding a temporary Code Cell at the end of the Notebook, executing it to get the output, and then deleting it.

I think this step can be skipped using the kernel-client api directly.

[ChengJiale150]

Currently, it's implemented by adding a temporary Code Cell at the end of the Notebook, executing it to get the output, and then deleting it.

I think this step can be skipped using the kernel-client api directly.

Sounds Good to me. fix it using kernel api in notebook.execute_cell

[echarles]

On https://github.com/datalayer/jupyter-kernel-client you can use simply the following to run code (not need for asyncio, tasks...)

import os

from platform import node
from jupyter_kernel_client import KernelClient

with KernelClient(server_url="http://localhost:8888", token="MY_TOKEN") as kernel:
    code = """import os
from platform import node
print(f"Hey {os.environ.get('USER', 'John Smith')} from {node()}.")
"""
    reply = kernel.execute(code)
    print(reply)
    assert reply["execution_count"] == 1
    assert reply["outputs"] == [
        {
            "output_type": "stream",
            "name": "stdout",
            "text": f"Hey {os.environ.get('USER', 'John Smith')} from {node()}.\n",
        }
    ]
    assert reply["status"] == "ok"

[ChengJiale150]

How can I control the timeout without asyncio? The timeout in kernel.execute do not represent for the timeout which I want.

[echarles]

OK, I see. timeout for code execution is sometimes tricky.

Happy to merge as-is. Later, it would be great to factor better timeout control in the kernel-client library.

[echarles]

LGTM Thx @ChengJiale150