➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rzn8tr
Recipients eric.araujo, ned.deily, rzn8tr
Date 2011-09-17.18:23:08
SpamBayes Score 1.9990675e-05
Marked as misclassified No
Message-id <F5096F52-B588-4F2A-9956-976DDEC40D4B@gmail.com>
In-reply-to <1316273717.54.0.744722114256.issue12956@psf.upfronthosting.co.za>
Content 
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@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@bugs.python.org>
> <http://bugs.python.org/issue12956>
> _______________________________________
History
Date User Action Args
2011-09-17 18:23:08rzn8trsetrecipients: + rzn8tr, ned.deily, eric.araujo
2011-09-17 18:23:08rzn8trlinkissue12956 messages
2011-09-17 18:23:08rzn8trcreate