|
From: | Ondřej Grover |
Subject: | Re: [O] Proposal and RFC for improving ob-python |
Date: | Thu, 10 Dec 2015 08:47:47 +0100 |
As I understand it (and if I'm remembering correctly), there are at
least three issues with ob-python sessions:
So for non-session code and value results, the main idea is to get rid
of the need for "return" at the end?
This seems useful to me. Requiring a trailing "return", which is a
syntax error when the code is taken by itself, is a quirk of the
implementation (the code ends up being wrapped in a function to get the
return value). Also, it would allow switching from ":results value" to
":results output" without needing to remove "return" in order to avoid a
syntax error.
But what about when :results != value? Doesn't your proposal only
handle returning the last value?
[Prev in Thread] | Current Thread | [Next in Thread] |