emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Edmund Christian Herenz <christian.herenz@astro.su.se>
To: emacs-orgmode@gnu.org
Subject: Bug: Tangling python code results in mixed tabs and spaces, incomaptible with python3 [9.1.4 (9.1.4-dist @ /home/ehere/emacs-scripts/org-9.1.4/lisp/)]
Date: Wed, 20 Dec 2017 19:24:48 +0100	[thread overview]
Message-ID: <20171220182448.6ltm4m4emmt7ftxv@knuspertop> (raw)


The following python code uses only whitespaces for the different
indentdation levels:

a_list = ['elem1',
          'elem2',
          'elem3']

for elem in a_list:
    print(elem)
    for char in elem:
        print char

I enter this code into a SRC block with

#+BEGIN_SRC python :tangle blank_test.py

#+END_SRC

by pressing C-' inside the block (which opens the editing buffer
python-mode).  Then I press C-' again, after which I tangle the code
to blank_test.py by pressing C-u C-c C-v C-t.  The resulting file
blank_test.py will contain a mix of tabs and spaces for the different
intendation levels.  (I checked this with whitespace.el).

Above behaviour is a bug, since Python3 forbids mixing of spaces and
tabs. (Python2 is more relaxed about mixing of tabs and spaces). Thus,
the above code, syntactical correctly entered into an OrgSrc buffer,
will result in code that can not be run in python3 when tangled from
an org-mode file.

Emacs  : GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5)
 of 2017-09-12 on hullmann, modified by Debian
Package: Org mode version 9.1.4 (9.1.4-dist @ /home/ehere/emacs-scripts/org-9.1.4/lisp/)

next             reply	other threads:[~2017-12-20 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 18:24 Edmund Christian Herenz [this message]
2017-12-21 13:56 ` Bug: Tangling python code results in mixed tabs and spaces, incomaptible with python3 [9.1.4 (9.1.4-dist @ /home/ehere/emacs-scripts/org-9.1.4/lisp/)] Nicolas Goaziou

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=20171220182448.6ltm4m4emmt7ftxv@knuspertop \
    --to=christian.herenz@astro.su.se \
    --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

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).