Ihor Radchenko writes:
> LGTM! Feel free to push.
Pushed to bugfix (c81dba2fb) and merged to main (b49275acb). Pushed the
unit test as a separate commit to main only (8000b1120).
Jack Kamm writes:
> I think `python-shell-first-prompt-hook' is actually still triggered,
> but rather it is `org-babel-comint-wait-for-output' that is hanging
> while waiting for startup. However, we can just replace it with a
> `sleep-for' instead, because we now wait for
>
On Sun, Aug 27, 2023 at 2:26 PM Jack Kamm wrote:
> Ihor Radchenko writes:
>
> > Confirmed.
> >
> > It looks like `python-shell-first-prompt-hook' does not get triggered
> > in the described scenario with exit() and we enter infinite loop in the
> > code below.
>
> I think
Ihor Radchenko writes:
> Peter Mao writes:
>
>> Expectation: When running ob-python code blocks, I should be able to
>> kill the python session in the *Python* buffer and run another code
>> block (or the same one).
>>
>> Problem: ob-python works fine on the first execution, but after
>>
Peter Mao writes:
> Expectation: When running ob-python code blocks, I should be able to
> kill the python session in the *Python* buffer and run another code
> block (or the same one).
>
> Problem: ob-python works fine on the first execution, but after
> `exit()`ing the python session, it
Expectation: When running ob-python code blocks, I should be able to
kill the python session in the *Python* buffer and run another code
block (or the same one).
Problem: ob-python works fine on the first execution, but after
`exit()`ing the python session, it hangs without executing the code.
