pip does not support spaces in directories names

under Mac OS X 10.7

tareks:tmp tarek$ mkdir "some space"
tareks:tmp tarek$ cd some\ space/
tareks:some space tarek$ virtualenv --no-site-packages .
The --no-site-packages flag is deprecated; it is now the default behavior.
New python executable in ./bin/python
Installing setuptools............done.
Installing pip...............done.
tareks:some space tarek$ bin/pip install docutils
-bash: bin/pip: "/private/tmp/some: bad interpreter: No such file or directory

Or maybe that’s virtualenv ?

[AlexeyMK]

For folks looking for a simpler solution, I got https://github.com/pypa/pip/issues/923#issuecomment-19655227 to work pretty well, in a simpler mode. I only ever needed to call pip once (during an install script), so instead of saying

virtualenv .env
.env/bin/activate
pip install -r requirements.txt

I did

virtualenv .env
.env/bin/activate
python .env/bin/pip install -r requirements.txt

Solved my my problem - still a challenge to call pip outside of the script, but the incision is more narrow.

[Bilge]

I’m not really into Python and this just confirmed I don’t want to be. It’s taken 4 years to add support for a space, and only to some platforms.