How to work with virtualenv? about pippel

[dakra]

I use https://github.com/porterjamesj/virtualenvwrapper.el and that works well, too.

Imho it's ok for pipple to just use the current active python version in emacs.
How you set your python version is up to the user then.. either pyvenv, virtualenvwrapper or by hand. No need to replicate that functionality in pippel.

[brotzeit]

I use pyvenv and it works without problems. However I don't know what pyvenv does in addition to setting python-shell-virtualenv-root. I will try to figure it out.

[Sarcasm]

Ah pyvenv ok, a quick look seems to indicate that it modifies exec-path: https://github.com/jorgenschaefer/pyvenv/blob/91c47b8d2608ccbcac2eba91f0e36b422101ce55/pyvenv.el#L172 end the environment variables.

It may be non-trivial to implement for pippel maybe I should just use pyvenv...?

[brotzeit]

I want to avoid additional dependencies, so I guess I have to find a way to get this to work without pyvenv. I like it, but I also didn't try anything else ;)

[arifer612]

Closed as I do not wish to look into this any further. I believe that using the active python environment is the right way to use pippel. If you intend to use specific virtual environment managers, I would suggest you to activate the virtual environment (e.g. pyvenv-activate for pyvenv) before executing pippel. This would reduce any ambiguity of its usage.