From: William Henney <whenney@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Karl Voit <news1142@karl-voit.at>, emacs-org <emacs-orgmode@gnu.org>
Subject: Re: Mixing Python2 and Python3 blocks in one file
Date: Thu, 19 May 2016 14:21:14 -0500 [thread overview]
Message-ID: <CAKchnZPUWQrj1cCvbJV8DzVYPak1G-u3bF5ZHtQiCSjYGAivwA@mail.gmail.com> (raw)
In-Reply-To: <m27feqqj7p.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]
On Thu, May 19, 2016 at 8:18 AM, Ken Mankoff <mankoff@gmail.com> wrote:
>
> Thanks for the example. This makes conda + Org work better than it has for
> me in the past. Unfortunately, one major issues is editing and running code
> outside of Org via (org-edit-special). Perhaps elpy will support conda
> environments soon.
>
>
I think Elpy works fine with conda environments - you just have to call
pyvenv-activate with the desired path.
You have inspired me to try and automate this for org source blocks (see
org snippets below). It is a bit clunky, but I got it to work. Let me
know what you think, and any stylistic corrections are welcome (my lisp
skills are sadly lacking).
* Automating Elpy virtual env configuration in babel source editing buffer
+ This function will automatically activate the virtual environment that
corresponds to the current python executable path
+ It should be a harmless no-op if we are not in a python buffer
#+BEGIN_SRC emacs-lisp
(defun wjh/elpy-pyvenv-activate-from-babel-info (info)
"Activate relevant conda virtual env in Babel source editing buffer.
The :python source block parameter is inspected to determine the venv."
(let* ((python-command (or (cdr (assoc :python (nth 2 info)))
org-babel-python-command))
(venv (replace-regexp-in-string "/bin/python$" ""
python-command)))
(when (string-match "/envs/" venv)
(pyvenv-activate (expand-file-name venv)))))
#+END_SRC
+ Then we need to make sure it is run whenever we edit a babel source block
by doing something like =(wjh/elpy-pyvenv-activate-from-babel-info
org-src--babel-info)=, and also to do =(pyvenv-deactivate)= when we leave
+ Unfortunately, there are no actual hooks that I can find for
=org-edit-src-code= or =org-edit-src-exit=
+ For the activation part we can co-opt the =org-babel-edit-prep:python=
function:
#+BEGIN_SRC emacs-lisp
(defun org-babel-edit-prep:python (info)
(wjh/elpy-pyvenv-activate-from-babel-info info))
#+END_SRC
+ Although this will break if =ob-python.el= decides to define
=org-babel-edit-prep:python= one day
+ For the deactivation part, I can't see any other way than to use advice
#+BEGIN_SRC emacs-lisp
(advice-add 'org-edit-src-exit :after #'pyvenv-deactivate)
#+END_SRC
+ One thing we have to remember is to install the elpy python package and
dependencies in each virtual environment. For instance:
#+BEGIN_SRC sh
source activate myenv
pip install elpy rope_py3k importmagic autopep8 yapf jedi
#+END_SRC
--
Dr William Henney, Instituto de Radioastronomía y Astrofísica,
Universidad Nacional Autónoma de México, Campus Morelia
[-- Attachment #2: Type: text/html, Size: 3714 bytes --]
next prev parent reply other threads:[~2016-05-19 19:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 8:31 Mixing Python2 and Python3 blocks in one file Karl Voit
2016-05-08 15:13 ` 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 [this message]
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
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=CAKchnZPUWQrj1cCvbJV8DzVYPak1G-u3bF5ZHtQiCSjYGAivwA@mail.gmail.com \
--to=whenney@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
--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 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).