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

Ha. How fun :)

We take different aproaches though.

Repo link for reference: https://github.com/tbug/vpython

Mine expects you to know virtualenv and how it works, and also that you explicitly install it. Same goes for dependencies.

My needs where to avoid sourcing the virtualenv, so i wrote the tool to fix just that. Also, i built mine to resolve symlinks and be usable as the shebang in your python scripts, which is pretty neat when writing command line tools.

Ah, discovering it from the directory. I considered this in analogy with the way vagrant works.

Downside is, ofc, that compared to just running something inside a virtualenv shell, vpython takes forever (up to 100ms-ish on my machine) to find the virtualenv, and set the correct env variables.

Most of my projects are long running though (webservers, number crunchers, etc), so the extra miliseconds it takes to load is really not that important.