Due to the way the shell or kernel parses the shebang, you can’t have spaces in the path to the interpreter:

http://lists.gnu.org/archive/html/bug-bash/2008-05/msg00053.html

The solution is to separate your virtualenv from the directory containing your code.  (virtualenvwrapper works in that way for example.)  virtualenv’s job is to have a copied Python with an isolated site-packages; it does not matter whether the Python is in your project directory (./bin/python) or anywhere else (~/venvs/strategist/bin/python).