Simon Cruanes

Done. @andrewray I think we might try a 0.1 alpha release relatively soon…

We need to have a full-fledged kernel (iocaml?) to validate that the kernel API is sufficient, and that the protocol is correctly implemented.

So far, we expose `Client.Kernel.t` as the main structure to be provided by implementation. Should we use a functor instead? Also need to list what is missing.

Yes indeed. Would you be willing to migrate iocaml here, and try and use the new API in it? I will migrate my own project (easy, since it already uses...

If you have time to look at the current API, it would be great! :-)

I've been using mime types myself (can at least display a .png in the notebook after base64 encoding) but not the stdio part. However, it should not have changed much,...

I think that reading stdin/printing on stdout should be done on the frontend side (jupyter-console, etc.), so not a concern to the kernel itself. Of course if some executed code...

https://jupyter-client.readthedocs.io/en/latest/messaging.html using this as a ref, btw. Will look into the "stream" part tomorrow.

I added a `Client_main` module that makes it easy to write a kernel server. Now writing a kernel is almost only writing the relevant functions (execute, complete, etc.)

I now have two (basic) kernels on top of that library. @andrewray any news from the iocaml side? I suppose you've been busy with other things, but it'd be nice...