"Barton, Mark" writes:
> Do we need to worry about the note about not appropriate for large blocks of
> code or does that not apply in this case with the way you implemented it.
> (org-babel-comint-wait-for-output BUFFER)
>
> Wait until output arrives from BUFFER.
> Note: this is only safe when
On Aug 27, 2022, at 6:30 PM, Ihor Radchenko
mailto:yanta...@gmail.com>> wrote:
* lisp/ob-python.el (org-babel-python-initiate-session-by-key): Do not
rely on 10ms delay to initialize Python. Wait until python process is
initialized using `org-babel-comint-wait-for-output'.
---
"Barton, Mark" writes:
> I tried something that was suggested last September 14th by Augusto Stoffel.
> I had not tried it because changing the sleep from 10 to 90 was my workaround.
> One thing that might work is to block until the shell is ready with something
> like
>
> (run-python)
>
I will work on getting more details this weekend. It looked like the buffer
passed to org-babel-comint-wait-for-output was missing the "earmuffs". I tried
adding the earmuffs with the org function for that but although I got passed
that error, I messed up my python session and the following
> On Aug 27, 2022, at 11:59 AM, Barton, Mark wrote:
>
>
>
>> On Aug 27, 2022, at 7:11 AM, Ihor Radchenko wrote:
>>
>> ---
>> lisp/ob-python.el | 8
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/lisp/ob-python.el b/lisp/ob-python.el
>> index
On Aug 27, 2022, at 7:11 AM, Ihor Radchenko
mailto:yanta...@gmail.com>> wrote:
---
lisp/ob-python.el | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lisp/ob-python.el b/lisp/ob-python.el
index 932aca08e..2ad907bd8 100644
--- a/lisp/ob-python.el
+++
Lars Ingebrigtsen writes:
>> Could you please elaborate what the problem is?
>> There have been multiple issues in this thread and the one previously
>> reported to Org ML is solved on Emacs side.
>
> It's this bit:
>
>> So I found if I extend the sleep-for in ob-python from 10 ms to 90 ms,
>>
Ihor Radchenko writes:
> Lars Ingebrigtsen writes:
>
>> The bug on the Emacs side was fixed by Augusto's patch, I think, but
>> there's a remaining problem in ob-python, so I'm reassigning this bug
>> report to org-mode.
>
> Could you please elaborate what the problem is?
> There have been
Lars Ingebrigtsen writes:
> The bug on the Emacs side was fixed by Augusto's patch, I think, but
> there's a remaining problem in ob-python, so I'm reassigning this bug
> report to org-mode.
Could you please elaborate what the problem is?
There have been multiple issues in this thread and the
