Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to work with virtualenv? #8

Closed
Sarcasm opened this issue Mar 23, 2017 · 5 comments
Closed

How to work with virtualenv? #8

Sarcasm opened this issue Mar 23, 2017 · 5 comments

Comments

@Sarcasm
Copy link

Sarcasm commented Mar 23, 2017

Hello,

I was wondering how to list the packages only from my virtualenv?

I have python-shell-virtualenv-root properly configured but it does not look like to be sufficient even if I saw some references to it in the code.

@brotzeit
Copy link
Collaborator

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
Copy link
Author

Sarcasm commented Mar 24, 2017

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
Copy link
Collaborator

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 ;)

@dakra
Copy link

dakra commented Mar 26, 2017

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.

@arifer612 arifer612 added the stale label Dec 5, 2021
@arifer612
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants