emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: [Babel] Strange bug in org-babel with python
Date: Wed, 11 Nov 2009 23:58:15 -0300	[thread overview]
Message-ID: <4afb79cc.c701be0a.75f3.7f34@mx.google.com> (raw)
In-Reply-To: <87pr7or2q5.fsf@stats.ox.ac.uk>


Hi Dan,

Thank you for the solution and specially for the explanation.  The
real problem was not understanding what was wrong. But with the
explanation in the other thread (that you also added in worg) thinks
make sense now.

- Darlan


At Wed, 11 Nov 2009 19:44:34 -0500,
Dan Davison <davison@stats.ox.ac.uk> wrote:
> 
> Darlan Cavalcante Moreira <darcamo@gmail.com> writes:
> 
> > Hello org-users,
> >
> > Today I was bitten by a weird behavior when executing some python
> > blocks with org-babel that really confused me, but after some trying
> > and error I was able to isolate the problem.
> >
> > When a block has an import statement such as
> > ,----
> > | from some_module import *
> > `----
> > it works with :results output, but not with :results value.
> 
> Hi Darlan,
> 
> Thanks for your helpful observations in this thread and the other
> one. I'm fairly happy with the solution we've arrived at, but the
> example you give above actually still won't work in :result value
> non-session. The reason is that in that scenario (and only that one), in
> order to compute the value of the block, org-babel wraps the code in a
> function and evaluates that function.
> 
> So the rules are now: in ':results value' non-session mode, you have to
> write code that is valid inside a function, and it seems that in python
> that is not true for
> 
> from some_module import *
> 
> I only learned this when studying your post. It seems that it's just the
> import * which is a problem; explicitly importing individual components
> or named modules is fine. So unless anyone knows better, I guess the
> answer is, Don't Do That :)
> 
> There's a working version of your example below that avoids import *,
> with the new necessary 'return' statements added.
> 
> Dan
> 
> 
> --------------------------------------------------------
> * dc
> #+begin_src python :tangle test :results silent
>   def double_input(a):
>       return a*2
> #+end_src
> 
> #+begin_src python :results value
>   import test
>   
>   def times_four(a):
>       return test.double_input(a)*2
>   
>   if __name__ == '__main__':
>       print "Value is %s" % times_four(10)
>       return times_four(10)
> #+end_src
> 
> #+resname:
> : 40
> 
> 
> #+begin_src python :results value
>   from test import double_input
>   
>   def times_four(a):
>       return double_input(a)*2
>   
>   if __name__ == '__main__':
>       print "Value is %s" % times_four(10)
>       return times_four(10)
> #+end_src
> 
> #+resname:
> : 40
> --------------------------------------------------------
> 
> 
> 
> >
> > The content of simple file to reproduce the problem is showed below
> >
> > --------------- Cut here -----------------------------------
> > * Test Org-babel
> >
> > #+begin_src python :tangle test :results silent
> >   def double_input(a):
> >       return a*2
> > #+end_src
> >
> > #+begin_src python :results value
> >   import test
> >   
> >   def times_four(a):
> >       return test.double_input(a)*2
> >   
> >   if __name__ == '__main__':
> >       print "Value is %s" % times_four(10)
> >       times_four(10)
> > #+end_src
> >
> > #+begin_src python :results value
> >   from test import *
> >   
> >   def times_four(a):
> >       return double_input(a)*2
> >   
> >   if __name__ == '__main__':
> >       print "Value is %s" % times_four(10)
> >       times_four(10)
> > #+end_src
> > --------------- End of cut ---------------------------------
> >
> > To reproduce the problem, tangle the file to create test.py from the
> > first block. Then executing the second block (which has no import *)
> > works with either :results output or :results value.
> >
> > However, the third block, (which uses import *) only works if executed
> > with :results output. I can't see the reason for this since the code
> > is right and works in a python buffer as expected.
> >
> > - Darlan
> >
> >
> >
> >
> > _______________________________________________
> > Emacs-orgmode mailing list
> > Remember: use `Reply All' to send replies to the list.
> > Emacs-orgmode@gnu.org
> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2009-11-12  2:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 23:26 [Babel] Strange bug in org-babel with python Darlan Cavalcante Moreira
2009-11-12  0:44 ` Dan Davison
2009-11-12  2:58   ` Darlan Cavalcante Moreira [this message]

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=4afb79cc.c701be0a.75f3.7f34@mx.google.com \
    --to=darcamo@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /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).