Difference between /path/to/env/bin/python setup.py and python setup.py in virtualenv

Question

This is a silly question but here it goes.

Usually, when I need to install a package in a virtual environment that for some reason is not playing nice with PIP , I activate such environment and then run /path/to/env/bin/python setup.py. This works fine but I have seen that some people just run python setup.py. Is it an omission of the full path? Or maybe, provided the virtual environment is activated, python setup.py installs the package in a virtual environment automatically. I don't know which one is correct.

Note: I don't want to mess up my clean Linux installation testing the hard way, so I thought it would be better to ask here.

Marcin · Accepted Answer · 2013-07-19 18:19:42Z

1

If you have activated the virtualenv in your shell, there is no difference. The obvious difference is that using the explicit path means you'll definitely get the version you expect.

answered Jul 19, 2013 at 18:19

Marcin

50.1k18 gold badges137 silver badges207 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

r_31415 Over a year ago

You mean in case I forget to activate the environment and then use python setup.py? Then activating the environment AND using the full path is redundant?

Collectives™ on Stack Overflow

Difference between /path/to/env/bin/python setup.py and python setup.py in virtualenv

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related