From: Eric Schulte <schulte.eric@gmail.com>
To: William Henney <whenney@gmail.com>
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: [babel] Setting python interpreter version on per-block or per-subtree basis
Date: Fri, 25 Apr 2014 12:04:42 -0600 [thread overview]
Message-ID: <871twl2slh.fsf@gmail.com> (raw)
In-Reply-To: <CAKchnZOjkRq3NUyQuEY2APAJgTuvwCGt--KBT0VtQkSV1FDraw@mail.gmail.com> (William Henney's message of "Fri, 25 Apr 2014 11:29:59 -0500")
I've just applied this patch. Thanks for the very attached nice test
and demonstration file.
Best,
William Henney <whenney@gmail.com> writes:
> Dear Sacha, Ian, and Eric
>
> Thanks very much for your replies. Sacha's way is a clever idea and works
> fine, but I think Eric's patch is the best solution in the long term.
> Please see attached test file - the patch works perfectly. Although I did
> have to study the manual carefully to work out how get it to work using the
> #+call: syntax. The key is to use "inside header arguments". Ian's
> solution with shebang works when tangling but not for direct evaluation of
> the source block.
>
> Cheers
>
> Will
>
>
>
>
> On Fri, Apr 25, 2014 at 10:27 AM, Eric Schulte <schulte.eric@gmail.com>wrote:
>
>> The attached patch should allow the specification of the python command
>> through a new :python header argument. E.g.,
>>
>> #+begin_src python :python /path/to/python2
>> return 1 + 2
>> #+end_src
>>
>> If someone who actually uses python could confirm that it works as
>> expected then I'll be happy to apply it.
>>
>>
>>
>> Best,
>> Eric
>>
>> William Henney <whenney@gmail.com> writes:
>>
>> > Hi
>> >
>> > Is there an easy way to specify the python version to use for a
>> particular
>> > block or sub-tree?
>> >
>> > My use case is that I have mainly migrated to python 3, but there is
>> still
>> > the occasional library that has not been updated yet, so I need to fall
>> > back to python 2.7 for some tasks.
>> >
>> > I can work around the problem by putting the python 2 code in a separate
>> > org file and use
>> >
>> > # Local Variables:
>> > # org-babel-python-command: "/path/to/python2"
>> > # End:
>> >
>> > but keeping everything in the same file would be preferable.
>> >
>> > Thanks
>> >
>> > Will
>>
>> --
>> Eric Schulte
>> https://cs.unm.edu/~eschulte
>> PGP: 0x614CA05D
>>
>>
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
prev parent reply other threads:[~2014-04-25 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 17:04 [babel] Setting python interpreter version on per-block or per-subtree basis William Henney
2014-04-25 1:59 ` Sacha Chua
2014-04-25 9:00 ` Ian Barton
2014-04-25 15:27 ` Eric Schulte
2014-04-25 16:29 ` William Henney
2014-04-25 18:04 ` Eric Schulte [this message]
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=871twl2slh.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=whenney@gmail.com \
/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).