Hi Dan,
On Thu, Oct 8, 2009 at 4:11 PM, Dan Davison wrote:
> Juan Reyero writes:
>> #+begin_src python :session :results output
>> 2
>> #+end_src
>>
>> #+resname:
>> : 2
>> : 2
>>
>> (expected nothing, which is what I get if I remove the :session).
>
> An understandable expectation. In non-sess
Juan Reyero writes:
[...]
>> --8<---cut here---start->8---
>> ** persistent python
>> #+begin_src python :session :results silent
>> import types
>> #+end_src
>>
>> #+begin_src python :session
>> types.FunctionType
>> #+end_src
>>
>> #+resname:
>> : function
Hi,
On Wed, Oct 7, 2009 at 9:17 PM, Eric Schulte wrote:
> As you described below the :session environment can be used to deal with
> the need for required "stage setting" source-code blocks, however there
> is currently no way when directly executing a block to specify that some
> other block in
Eric,
Thanks a lot for your quick response. I have tried your suggestion
and it does work, but it behaves in an unexpected way when I do some
minor modifications. Please see below.
On Wed, Oct 7, 2009 at 8:48 PM, Eric Schulte wrote:
>> I am trying to define buffer-wide initializations in org-b
Hi,
This brings up a need for further Org-babel development.
As you described below the :session environment can be used to deal with
the need for required "stage setting" source-code blocks, however there
is currently no way when directly executing a block to specify that some
other block in the
Juan Reyero writes:
> Greetings,
>
Hi,
>
> I am trying to define buffer-wide initializations in org-babel, so that I can
> import a python module once
> and then use its exported symbols in all the code chunks throughout the
> buffer. Is there a way to do it?
> I have tried all the obvious
Greetings,
I am trying to define buffer-wide initializations in org-babel, so that I
can import a python module once and then use its exported symbols in all the
code chunks throughout the buffer. Is there a way to do it? I have tried
all the obvious approaches and none seems to work. (My hope w
