Fixed in r1336 exactly like proposed above. Would've wanted to use subprocess.call
which handles escaping automatically, but since we still want to keep Python 2.3
support couldn't do that.

Heiko, could you test this on your environment if you still have Python installed
into a directory with spaces? I wouldn't want to install extra Pythons on my normal
machines and don't have any virtual environment available. I already tested that
install.py works on Windows and Linux when there are no spaces in sys.executable. You
can simply copy the latest version over earlier from
http://robotframework.googlecode.com/svn/trunk/install.py

I updated the summary because the same problem appears also if source is checked out
from version control. 

Notice that installation is still likely to fail if the source is unzipped or checked
out into a directory with spaces in path. Handling also that isn't exactly trivial as
 issue 166  shows. In there the final solution was to call Python script directly (i.e.
without having sys.executable) but that doesn't work here since it will use system's
default Python and we want to use the same sys.executable that was used to start
install.py to run also setup.py.

Yes, the installation works with the correction. The installed robotframework works, too.

I didn't try to install robot into a directory with spaces (yet). Maybe I can try
later and raise an issue if it fails.

Thanks for testing Heiko.

The other issue I mentioned is not related to installing RF to directory with spaces
(RF is installed under Python so that ought to work already now). It can be that if
you extract the tar.gz package into a directory with spaces (or checkout code into
such directory from SVN) running install.py there fails.

(No comment was entered for this change.)