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

Change by Irit Katriel : -- resolution: -> wont fix stage: needs patch -> resolved status: pending -> closed ___ Python tracker ___ ___

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

Irit Katriel added the comment: LMO, if you are still interested in this issue, could you be more specific about where you think this should be documented? If you want to create a patch, go for it. -- nosy: +iritkatriel status: open -> pending ___

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

LMO 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 added the comment: > >> While I'm sympathetic to supporting arbitrary path

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

Éric Araujo 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 th

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

Ned Deily added the comment: It turns out that supporting a framework path name that contains spaces (or other special characters) is a much more pervasive change that I had originally expected. That's because the path specified by ./configure --enable-framework= also becomes the default for