Virtualenv's bin/activate is Doing It Wrong

#1

Post by kefeizhou » Wed, Feb 27, 2013, 8:42 AM UTC

Virtualenv's bin/activate is Doing It Wrong
gist.github.com

Re: Virtualenv's bin/activate is Doing It Wrong

#2

Post by lifeisstillgood » Wed, Feb 27, 2013, 9:36 AM UTC

Venv is one of the pieces of sanity in the python packaging deployment world and any improvements welcome - this goes on my List if things to think hard about

Re: Virtualenv's bin/activate is Doing It Wrong

#3

Post by Comkid » Wed, Feb 27, 2013, 10:29 AM UTC

Reading the Google Groups responses, he's officially created a http://xkcd.com/1172/ situation heh

Re: Virtualenv's bin/activate is Doing It Wrong

#4

Post by kennu » Wed, Feb 27, 2013, 10:57 AM UTC

But what will be the added CO2 footprint of launching so many unnecessary shells!

Also, I don't like the prospect of having to hit Ctrl-D twice to logout.

Re: Virtualenv's bin/activate is Doing It Wrong

#5

Post by avdd_ » Wed, Feb 27, 2013, 11:30 AM UTC

Comkid wrote: post #3

Reading the Google Groups responses, he's officially created a http://xkcd.com/1172/ situation heh

I assume you mean this thread

https://groups.google.com/d/topic/python-virtualenv/XzI8GStv...

Re: Virtualenv's bin/activate is Doing It Wrong

#6

Post by __alexs » Wed, Feb 27, 2013, 12:07 PM UTC

kennu wrote: post #4

But what will be the added CO2 footprint of launching so many unnecessary shells! Also, I don't like the prospect of having to hit Ctrl-D twice to logout.

Then type 'exec inve' instead of just 'inve.'

Re: Virtualenv's bin/activate is Doing It Wrong

#7

Post by kennu » Wed, Feb 27, 2013, 12:11 PM UTC

__alexs wrote: post #6

kennu wrote: post #4

But what will be the added CO2 footprint of launching so many unnecessary shells! Also, I don't like the prospect of having to hit Ctrl-D twice to logout.

Then type 'exec inve' instead of just 'inve.'

Perhaps that makes sense. Actually I usually type 'workon myproject' (using virtualenvwrapper, because it provides a nice standard location and activation command for virtualenvs), so maybe this could all be transparent.

Re: Virtualenv's bin/activate is Doing It Wrong

#8

Post by the_mitsuhiko » Wed, Feb 27, 2013, 12:15 PM UTC

The fact that it does not use a subshell makes it useful. You can trivially use it in bash scripts and cronjobs.

Re: Virtualenv's bin/activate is Doing It Wrong

#9

Post by IgorPartola » Wed, Feb 27, 2013, 12:25 PM UTC

the_mitsuhiko wrote: post #8

The fact that it does not use a subshell makes it useful. You can trivially use it in bash scripts and cronjobs.

Why can you not do?:

  #!/usr/bin/virtual-bash my-env
  
  echo hello

Edit: in fact something like /usr/bin/virt-python my-env is much nicer than /var/lib/my-app/env/bin/python. Basically like virtualenvwrapper but for Python scripts that are not run interactively.

Re: Virtualenv's bin/activate is Doing It Wrong

#10

Post by the_mitsuhiko » Wed, Feb 27, 2013, 12:33 PM UTC

IgorPartola wrote: post #9

the_mitsuhiko wrote: post #8

The fact that it does not use a subshell makes it useful. You can trivially use it in bash scripts and cronjobs.

Why can you not do?: #!/usr/bin/virtual-bash my-env echo hello Edit: in fact something like /usr/bin/virt-python my-env is much nicer than /var/lib/my-app/env/bin/python. Basically like virtualenvwrapper but for Python scripts that are not run interactively.

I regularly write scripts that involve more than one virtualenv. At the moment this is trivial by just activating and deactivating envs from one script. Starting subshells is complicated because communication into the shell barely exists. Worse than that is that the shebang only supports two arguments and is heavily length limited.