From: "Tobias Müller" <mllertobias@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Bug: Python session raises indentation error [9.2.6 (9.2.6-elpa @ /home/tobias/.emacs.d/elpa/org-9.2.6/)]
Date: Mon, 14 Oct 2019 19:55:52 +0200 [thread overview]
Message-ID: <8bc94355-0c14-4b43-b060-7dd4db42f32b@gmx.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
Dear org-mode developer,
I have discovered the following issue with Python code-blocks: Using the
:session header argument leads to errors of the type IndentationError:
expected an indented block if the code block contains indented regions
with empty lines. An example code-block which produces this kind of
error is the following:
#+begin_src python :session
for k in range(3):
print(k)
#+end_src
removing the :session header argument leads to correct execution of the
code block. The same is true if the :results output header argument is used.
If the blank line within the for-loop is removed the loop also gets
executed correctly, however after executing the block the error
NameError: name '_' is not defined is raised in the buffer of the Python
session.
The generated info-file is attached to this mail.
Best regards,
Tobias Müller.
[-- Attachment #1.2: Type: text/html, Size: 1270 bytes --]
[-- Attachment #2: info --]
[-- Type: application/octet-stream, Size: 251133 bytes --]
next reply other threads:[~2019-10-14 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 17:55 Tobias Müller [this message]
2019-10-14 18:24 ` Bug: Python session raises indentation error [9.2.6 (9.2.6-elpa @ /home/tobias/.emacs.d/elpa/org-9.2.6/)] Tobias Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8bc94355-0c14-4b43-b060-7dd4db42f32b@gmx.de \
--to=mllertobias@gmx.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).