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 vstinner
Recipients ocean-city, vstinner
Date 2010-09-10.11:25:00
SpamBayes Score 2.8246022e-08
Marked as misclassified No
Message-id <1284117909.06.0.159808502364.issue9819@psf.upfronthosting.co.za>
In-reply-to
Content
> "dir" command cannot print filename correctly, though.

Who cares? We just have to be able to create a file with a name containing non encodable characters, list the directory, and then remove this evil file.

--

With r84666, Python uses "-\u5171\u6709\u3055\u308c\u308b" suffix for TESTFN_UNENCODABLE. Does it fix the issue on your host?

I attached an improved version of find_unencode_filename.py (with more code pages).

--

> > TESTFN_UNICODE_UNDECODEABLE (2.x)
> This is a typo fixed by r83987 in py3k.

I backported the fix to 2.7 (r84667).
History
Date User Action Args
2010-09-10 11:25:09vstinnersetrecipients: + vstinner, ocean-city
2010-09-10 11:25:09vstinnersetmessageid: <1284117909.06.0.159808502364.issue9819@psf.upfronthosting.co.za>
2010-09-10 11:25:02vstinnerlinkissue9819 messages
2010-09-10 11:25:02vstinnercreate