[babel] Possible bug: (mis)handling tuples for :return value in Python [7.4 (release_7.4.153.ga0b8)]

[babel] Possible bug: (mis)handling tuples for :return value in Python [7.4 (release_7.4.153.ga0b8)]

[Scott May]

I do not think that =org-babel-read= is correctly handling Python
tuples that are returned from source blocks.

If I execute the following source block:
#+begin_src python :results value
  return (1,2)
#+end_src

I get the following error message:
: Symbol's function definition is void: 1\,

The Python output for this source block is =(1,2)=, which =org-babel-read=
interprets as lisp and tries to eval.

I can work around the problem using either a Python list:
#+begin_src python :results value
  return [1,2]
#+end_src

or by using =:results output=
#+begin_src python :results output :session
  (1,2)
#+end_src

Regards,
Scott


Emacs  : GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.21.6)
 of 2010-09-01 on rhenium, modified by Debian
Package: Org-mode version 7.4 (release_7.4.529.gb23d)



      

Re: [babel] Possible bug: (mis)handling tuples for :return value in Python [7.4 (release_7.4.153.ga0b8)]

[Eric Schulte]

Scott May <bscottmay@yahoo.com> writes:

> I do not think that =org-babel-read= is correctly handling Python
> tuples that are returned from source blocks.
>
> If I execute the following source block:
> #+begin_src python :results value
>   return (1,2)
> #+end_src
>
> I get the following error message:
> : Symbol's function definition is void: 1\,
>
> The Python output for this source block is =(1,2)=, which =org-babel-read=
> interprets as lisp and tries to eval.
>
> I can work around the problem using either a Python list:
> #+begin_src python :results value
>   return [1,2]
> #+end_src
>
> or by using =:results output=
> #+begin_src python :results output :session
>   (1,2)
> #+end_src
>
> Regards,
> Scott
>

Hi Scott,

This issue has come up a couple of times recently.  I just pushed up a
fix.  Please let me know if you run into any further issues.

Thanks -- Eric

Re: [babel] Possible bug: (mis)handling tuples for :return value in Python [7.4 (release_7.4.153.ga0b8)]

[Scott May]

> 
> Hi  Scott,
> 
> This issue has come up a couple of times recently.  I just  pushed up a
> fix.  Please let me know if you run into any further  issues.
> 
> Thanks -- Eric
> 

Eric,

It works now. Thanks! 

Cheers,
Scott