Re: python sessions

[John Hendy <jw.hendy@gmail.com>]

On Sun, Mar 24, 2013 at 2:47 AM, Andreas Röhler
<andreas.roehler@easy-emacs.de> wrote:
> Am 23.03.2013 23:07, schrieb Eric Schulte:
>>
>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>
>>> Am 21.03.2013 08:43, schrieb Bastien:
>>>>
>>>> Hi Andreas,
>>>>
>>>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>>>
>>>>> Nonetheless, still thinking
>>>>>
>>>>> let-var session in
>>>>>
>>>>> org-babel-execute:python
>>>>>
>>>>> needs the fix.
>>>>
>>>>
>>>> I've not been following this thread, can you send a patch with
>>>> the fix and the reason for it?  Thanks in advance!
>>>>
>>>
>>> Hi Bastien,
>>>
>>> unfortunately my org-environment isn't ready yet for developing.
>>> Might take some time, but I'm on it.
>>
>>
>> I also haven't been following this thread.
>>
>> Forgetting a patch for the moment, is it possible to conclusively state
>> that there is or isn't a bug in the current ob-python handling and
>> naming of sessions?  If there is, is there a recipe for reproducing this
>> bug?
>>
>> Thanks,
>>
>
> Hi,
>
> Ista proved it works for him.
>
> <CA+vqiLHUWvGOgszTO9981NXXbYhnKmcB-rdHbDY8nEhYpzU-og@mail.gmail.com>
>

This opens up a compose window in gmail for me. I think this is the
thread you might have wanted to point to:
- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg68267.html

That only speaks to =:session name= argument <=> resultant python buffer names.

As Andreas pointed out, however, there *are* individuals having issues
with the actual code execution, and persistence across blocks with the
same :session names. That's another mystery I don't think we've
solved.

Ista and myself both get proper functionality, but session name
arguments don't create named buffers. Others are not getting proper
functionality.


John

> Maybe we all other have incomplete resp. not updated installations?
>
> Best regards,
>
> Andreas
>