From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: org-sbe: error when passing strings as parameters to/from Python blocks
Date: Thu, 14 Mar 2019 10:26:29 +0100 [thread overview]
Message-ID: <2019-03-14T09-43-42@devnull.Karl-Voit.at> (raw)
Hi!
I want to test/use Python with org-sbe:
#+NAME: classificationfm
#+BEGIN_SRC python :exports none :var prob :var impact
result = ""
if prob == 'high' and impact == 'high':
return 'A'
if prob == 'low' and impact == 'high':
return 'B'
if prob == 'high' and impact == 'low':
return 'C'
if prob == 'low' and impact == 'low':
return 'D'
return 'undefined'
#+END_SRC
(Yes, I should move to elif and the Python code might be coded with
less characters in general: this should not be the point here ;-) )
| prob | impact | class |
|------+--------+--------|
| high | high | #ERROR |
| low | high | #ERROR |
| high | low | #ERROR |
| low | low | #ERROR |
#+TBLFM: @2$3..@>$3='(org-sbe "classificationfm" (prob $1) (impact $2))
I'd expect to get the values of the "class" table column: A, B, C, D
instead of #ERROR.
Reading the manual, I found:
| NOTE: By default, string variable names are interpreted as
| references to source-code blocks, to force interpretation of a
| cell’s value as a string, prefix the identifier a "$" (e.g.,"$$2"
| instead of "$2" or "$@2$2" instead of "@2$2").
Therefore, I tried the following lines ...
#+TBLFM: @2$3..@>$3='(org-sbe "classificationfm" (prob "$1") (impact "$2"))
#+TBLFM: @2$3..@>$3='(org-sbe "classificationfm" (prob $$1) (impact $$2))
#+TBLFM: @2$3..@>$3='(org-sbe "classificationfm" (prob "$$1") (impact "$$2"))
... all with same error in the result.
My setup: Org mode version 9.1.6 on GNU Emacs 26.0.90 and GNU Emacs 25.1.1
I started a reddit thread[1]. In this thread, somebody was posting
this table showing the error:
#+NAME: myfunc
#+BEGIN_SRC python :var n="1"
return "ok"
#+END_SRC
| 10.3 | 9 | -18 | a | 14 | 11 | 1 |
| ok | ok | ok | #ERROR | ok | ok | ok |
#+TBLFM: @2='(org-sbe myfunc (n @1))
However, using the comment from the manual about strings, I
prepended the reference with "$" ...
| 10.3 | 9 | -18 | a | 14 | 11 | 1 |
| ok | ok | ok | ok | ok | ok | ok |
#+TBLFM: @2='(org-sbe mytestfunc (n $@1))
... which now looks OK ;-)
So, back to the initial situation: what is my error or do we have a
bug in Org?
[1] https://www.reddit.com/r/orgmode/comments/b0ll1v/embedding_python_code_in_table_formula/
--
get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
Personal Information Management > http://Karl-Voit.at/tags/pim/
Emacs-related > http://Karl-Voit.at/tags/emacs/
next reply other threads:[~2019-03-14 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 9:26 Karl Voit [this message]
2019-03-14 10:53 ` org-sbe: error when passing strings as parameters to/from Python blocks Daniel Herzig
2019-03-14 12:27 ` [bug] " Karl Voit
2019-03-14 15:37 ` Karl Voit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2019-03-14T09-43-42@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).