Jorgen Schäfer

Hm. That would mean that your `shell-file-name`, when invoked to run a script, does not set up virtualenvwrapper. Is that the case? Where do you set up virtualenvwrapper?

virtualenvwrapper suggests sourcing the .sh file in `.bashrc`, not `.bash_profile` … you might already have problems in a subshell this way. Hm. I guess pyvenv should export some of the...

I have no idea what might be causing this I'm afraid. If you find out, please let me know!

Sorry for the late reply. Yes, I can reproduce this. I do not know how to fix it. :-(

You can use `pyvenv-post-activate-hooks` to run a custom function after activation, and run whatever code you like there. I'm not sure if that solves your problem?

Does `python-shell-send-string-no-output` do what you want?

The best practice for using `pyvenv` is to stick to the best practice set up with `virtualenvwrapper`, i.e. do not put your virtualenvs into the same directory as your project...

If you do not use the normal virtualenvwrapper setup, you can use `M-x pyvenv-activate` like you'd use the `activate` script of a virtualenv.

You can use `pyvenv-tracking-mode` and set `pyvenv-workon` or `pavenv-activate` in the respective buffer? I usually don't, because switching virtualenvs takes time, so I juse use `pyvenv-workon` manually.

> But is there a way to actually have different venvs in different frames at least? I'm afraid virtualenvs are basically process-global. Buffers or frames make no difference there, they...