Peter Tittmann <[email protected]> writes: > Tested the `bba-ngnu-pending-contents' branch locally — the > callback-based async example (`my-use-callbacks' engine, elisp source > block with `:nasync yes') runs end-to-end. `org-babel-execute-src-block' > returns a reglock, the region locks, callbacks fire, the `#+RESULTS:' > table is populated correctly, and the reglock is released. Smoke-level > only; haven't exercised the threads, futur, or dynamic-block paths yet.
Thanks for testing! > One thing I want to flag: there's no integration code between > `org-pending' and `emacs-jupyter' yet on either side — `ob-jupyter.el' > has its own async-overlay path (`jupyter-org-pending-async-results'). > The validation you suggested against jupyter would mean writing a > bridge (a small `jupyter-org-pending-schedule' wrapper using > `:execute-with'). I'm happy to take that on, but I'd rather get FSF > copyright assignment in flight first so any patches can land. I'll > start that this week. Note that we are still discussing the overall design of the babel API. (See my latest email). My comments are currently on the level "can we reuse what is already there?", but it will already help to think ahead about whether the design is suitable for use cases needed for jupyter. You don't need copyright assignment to participate in the discussions ;) Note that copyright assignment may take some time, depending on the workload of FSF staff. Typically, between one a and a few weeks. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
