Ivar Fredholm writes:
> Hi Ihor, I have a prototype of what I mentioned earlier, at least for python.
> This supports asynchronous, synchronous, session, and session-less blocks.
> It's pretty messy but it helps to illustrate what I had in mind. Let me know
> what you think.
I am not sure
Hi Ihor, I have a prototype of what I mentioned earlier, at least for python.
This supports asynchronous, synchronous, session, and session-less blocks. It's
pretty messy but it helps to illustrate what I had in mind. Let me know what
you think.
Sent with Proton Mail secure email.
---
The Jupyter project is one approach to this. It currently has dozens of
kernels for different languages, and new kernels can certainly be made. The
emacs-jupyter package provides one implementation of an interface. It is
complex, and relies on a compiled module for the zeromq message passing
Tom Gillespie writes:
>> I am not even sure if all the babel backends support try-except.
>> Think about ob-gnuplot or, say, ob-latex.
>
> Indeed many do not. Defining some standard "features"
> for org babel language implementations is something that
> is definitely of interest so that we can
> I am not even sure if all the babel backends support try-except.
> Think about ob-gnuplot or, say, ob-latex.
Indeed many do not. Defining some standard "features"
for org babel language implementations is something that
is definitely of interest so that we can provide clear interfaces
for
Ivar Fredholm writes:
> I believe the two could be unified if we expand the functionality of
> the async filter to look for 'exception' tags. Then each language
> implementation must only put the org-babel src block in a try-except
> type construction and put the error message into the except
Hi, Ihor,
I believe the two could be unified if we expand the functionality of the async
filter to look for 'exception' tags. Then each language implementation must
only put the org-babel src block in a try-except type construction and put the
error message into the except block. The async
Ivar Fredholm writes:
> A session-less block can be executed by starting a session with a special
> name (say "*none") which always gets killed after block execution is
> completed. For interpreter-less languages, we could use the shell as an
> interpreter (for instance, if we wanted to
A session-less block can be executed by starting a session with a special name
(say "*none") which always gets killed after block execution is completed. For
interpreter-less languages, we could use the shell as an interpreter (for
instance, if we wanted to execute C, we could just start a
