From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Problem with python session Date: Sun, 09 Oct 2016 11:30:04 +0200 Message-ID: <87twclkgyr.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42344) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1btAQo-0002dU-7t for emacs-orgmode@gnu.org; Sun, 09 Oct 2016 05:30:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1btAQn-0001Bk-98 for emacs-orgmode@gnu.org; Sun, 09 Oct 2016 05:30:06 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:39206) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1btAQn-0001BO-31 for emacs-orgmode@gnu.org; Sun, 09 Oct 2016 05:30:05 -0400 In-Reply-To: (William Henney's message of "Thu, 6 Oct 2016 12:54:49 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: William Henney Cc: Florian Lindner , emacs-org Hello, William Henney 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