Well huh.

> Vpython is a tiny(-ish) bash script to help with your day to day virtualenv needs.

> * You don't have to worry about sourcing the activate script.

> * You don't have to point to your virtualenv path.

> just use vpython instead of python to invoke your scripts.

That's basically why I wrote vpython: I'm the author of this vpython[1], which isn't the same as yours, nor what the article is. (I suspect mine is a little more immature, as I've not worked on it for as long.) I guess similar needs beget similar utilities.

  [1]: https://github.com/thanatos/vpython