Could it be a poorly rewritten patch? Original Daniel Gerber's proposal works
for me.
diff --git a/lisp/ob-python.el b/lisp/ob-python.el
index 1457682..523fd70 100644 (file)
--- a/lisp/ob-python.el
+++ b/lisp/ob-python.el
@@ -137,7 +137,7 @@ specifying a variable of the same value.
Hi Miguel,
Miguel Ruiz rbeni...@yahoo.es writes:
Could it be a poorly rewritten patch? Original Daniel Gerber's
proposal works for me.
Can you tell what's wrong in the current version of ob-python.el
from git repo? Otherwise I'm not sure to understand.
Thanks,
--
Bastien
Sorry, Bastien
At this moment, in ob-python.el you can see:
(defun org-babel-python-var-to-python (var) Convert an elisp value to a python
variable.
Convert an elisp value, VAR, into a string of python source code
specifying a variable of the same value. (if (listp var) (concat [
(mapconcat
Confirmed. I just pulled the latest repository and it is fixed! Hooray, now
to finish exporting the manuscript I am trying to resubmit!
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Miguel Ruiz rbeni...@yahoo.es writes:
But I understand that Daniel Gerber's proposal is (note the last
line):
Got it now. Fixed, thanks!
--
Bastien
Hi all,
I am having a problem in 8.2.5 using a table as a data source for a python
block. I get this particular error: org-babel-python-var-to-python: Wrong
type argument: stringp, 1
It seems to be that the 1 is not a string, but a number.
Here is what I have to reproduce the problem. the table
John Kitchin jkitc...@andrew.cmu.edu writes:
Does anyone else see this?
Yes. I seem to have different default header args (e.g. :results value
rather than :results output for the first python block and the table
gets printed out as a table, not as a lisp list, for the elisp block)
but the last
