Shebang env/bin/python makes no sense

[onitake]

The interpreter specification env/bin/python won't do what it's supposed to on most Unix/GNU/Linux systems, as the path is neither absolute nor does it match a common location for the python binary.

For launching a script with the Python interpreter, the most common specification is:

#!/usr/bin/env python

The line is also listed on the Wikiepdia page: https://en.wikipedia.org/wiki/Shebang_(Unix)#Examples

Please fix this.

[smasty]

It makes perfect sense if you follow the instructions and install the requirements to a virtualenv.
However, a new version of this tool is in the works, which will handle instllation differently.

[onitake]

Good point, but not everybody uses virtualenv.

Also, all the resources I found concerning a virtualenv compatible shebang mention the line I posted above. Path mangling is managed happily by /usr/bin/env and it still makes no sense to put a relative path there.

But thanks for taking care of this!