From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Mixing Python2 and Python3 blocks in one file
Date: Sun, 8 May 2016 10:31:03 +0200 [thread overview]
Message-ID: <2016-05-08T10-21-00@devnull.Karl-Voit.at> (raw)
Hi!
Python2 and Python3 are two different languages. Unfortunately,
Org-mode only uses ~#+BEGIN_SRC python~ for both and uses
python-shell-interpreter to choose/switch the compiler.
Shouldn't Org-mode introduce ~#+BEGIN_SRC python2~ and ~#+BEGIN_SRC
python3~ to solve this issue in a clean way?
~#+BEGIN_SRC python~ can still default to python2.
I only found those sources/solutions:
http://thread.gmane.org/gmane.emacs.orgmode/47867
... file-variables to choose interpretor
http://thread.gmane.org/gmane.emacs.orgmode/47867
... workaround with #+srcname (I don't get yet)
--
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
next reply other threads:[~2016-05-08 8:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 8:31 Karl Voit [this message]
2016-05-08 15:13 ` Mixing Python2 and Python3 blocks in one file Karl Voit
2016-05-17 14:24 ` William Henney
2016-05-17 14:54 ` Karl Voit
2016-05-17 15:37 ` John Kitchin
2016-05-18 1:19 ` William Henney
2016-05-18 3:42 ` Thomas S. Dye
2016-05-18 7:11 ` Karl Voit
2016-05-18 7:10 ` Division of Org documentation: Org manual and Worg (was: Mixing Python2 and Python3 blocks in one file) Karl Voit
2016-05-18 8:10 ` Division of Org documentation: Org manual and Worg Daniele Pizzolli
2016-05-18 9:03 ` Rasmus
2016-05-18 10:08 ` Daniele Pizzolli
2016-05-18 10:18 ` Rasmus
2016-05-20 17:15 ` Daniele Pizzolli
2016-05-20 18:46 ` Rasmus
2016-05-18 10:18 ` Daniele Pizzolli
2016-05-18 13:45 ` Mixing Python2 and Python3 blocks in one file Ken Mankoff
2016-05-19 3:37 ` William Henney
2016-05-19 13:18 ` Ken Mankoff
2016-05-19 19:21 ` William Henney
2016-05-19 19:32 ` Ken Mankoff
2016-05-19 20:01 ` William Henney
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2016-05-08T10-21-00@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.