Ista, what OS are you on?  Maybe this (or part of it anyway) is only a
Windows problem?


On Wed, Mar 20, 2013 at 4:12 PM, Ista Zahn <istazahn@gmail.com> wrote:

> On Wed, Mar 20, 2013 at 3:53 PM, Andreas Röhler
> <andreas.roehler@easy-emacs.de> wrote:
> > Am 20.03.2013 20:42, schrieb Ista Zahn:
> >
> >> On Wed, Mar 20, 2013 at 2:43 PM, Andreas Röhler
> >> <andreas.roehler@easy-emacs.de> wrote:
> >>>
> >>>
> >>>> I guess it depends on the definition of "works". I don't get python
> >>>> buffers with the name of the :session variable.
> >>>
> >>>
> >>>
> >>> Reads as it works only with named sessions, but fails with unnamed
>
> Oops, sorry I totally misread this before. I guess my last email
> didn't make much sense!
>
> >>
> >>
> >> It fails to name the python process buffers.
> >
> >
> > May you try still an unnamed session as sent by OP?
>
> Unnamed sessions works as expected:
>
>
> #+BEGIN_SRC python :exports results :results output :session
>   def foo(x):
>     return(x+1)
>
> #+END_SRC
>
> #+RESULTS:
>
>
> #+BEGIN_SRC python :exports results :results output :session
>   def bar(x):
>     return(x+2)
>
> #+END_SRC
>
> #+RESULTS:
>
> #+BEGIN_SRC python :exports results :results output :session
>   print(foo(100))
>   print(bar(100))
>
> #+END_SRC
>
> #+RESULTS:
> : 101
> : 102
>
>
> >
> > Andreas
> >
>
>


-- 
Gary