Hello, William Henney <when...@gmail.com> writes:
> I can reproduce your problem. This is (arguably) a bug in ob-python when > using the vanilla python interpreter together with the :session argument. > You can work around it by putting a blank line after the for-loop in your > second code block. > > I say that it is arguable that this is a bug or not since you would have > exactly the same error if you were to literally type your code block in at > the python interactive prompt. That is, you have to give a second newline > in order to close the loop and return to the top-level prompt. However, it > is admittedly confusing to have different behavior with and without the > ":session" argument. Thank you for the analysis. Would you have a suggestion on how to improve the situation? Regards, -- Nicolas Goaziou
