[issue12956] builds fail when installing to --prefix with space in path name

[LMO]

LMO <raycores at gmail.com> added the comment:

I don't see supporting spaces as being important, either.  Since the failure is not obviously related to the presence of spaces, I would like to see the limitation documented.

> 
> Éric Araujo <merwok at netwok.org> added the comment:
> 
>> While I'm sympathetic to supporting arbitrary path names, I'm not sure
>> if it is worth the effort.
> 
> My sentiment too.  Supporting non-ASCII characters seems clearly important to me, as it’s a reasonable and common thing to run or install Python from a patch that may contain non-ASCII characters (a first name, “downloads” in French, etc.); supporting spaces is less important.
> 
> ----------
> nosy: +eric.araujo
> 
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue12956>
> _______________________________________

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12956>
_______________________________________