exec-path is changed if WORKON_HOME is set regardless either it is an active virtualenv session
Bug #1080794 reported by
Yaroslav Halchenko
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-mode.el |
Fix Released
|
High
|
Andreas Roehler | ||
Bug Description
Decided to give a try to recent changes (rev 1144) now and found that for any execution the path gets changed to what I have globally set in my .profile in WORKON_HOME -- imho that should not happen. WORKON_HOME only instructs where to keep virtualenvs, even if not currently using virtualenv, so it is imho incorrect to assume that I am working with virtualenv if this env variable is set.
When I use virtualenv I use it via virtualenvwrapper shell helper, and that one seems to set VIRTUAL_ENV variable pointing to current env I am 'workon'.
But even if I 'unset' it in the shell and restart emacs, running the script (C-c C-c) now changes to $HOME -- why??? makes impossible to use python-mode atm for any interactive work
| Changed in python-mode: | |
| milestone: | none → 6.1.0 |
| assignee: | nobody → Andreas Roehler (a-roehler) |
| importance: | Undecided → High |
| Changed in python-mode: | |
| status: | New → In Progress |
Revision history for this message
| Andreas Roehler (a-roehler) wrote | #1 |
| Changed in python-mode: | |
| status: | In Progress → Fix Committed |
| Changed in python-mode: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
replacing "WORKON_HOME" in defun py-execute-base, line 8948, by "VIRTUAL_ENV" should solve it