[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

STINNER Victor added the comment: > Thank you, your patch works. Ok, patch commited to 3.2 as r84710. Thanks for your feedback. -- ___ Python tracker ___ ___

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Hirokazu Yamamoto added the comment: Thank you, your patch works. E:\python-dev\py3k>py3k -m test.test_unicode_file test_directories (__main__.TestUnicodeFiles) ... ok test_single_files (__main__.TestUnicodeFiles) ... ok -- Ra

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Changes by STINNER Victor : Added file: http://bugs.python.org/file18845/unicode_file.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

STINNER Victor added the comment: > How about TESTFN_UNICODE (test_unicode_file) issue? File "e:\python-dev\py3k\lib\test\test_unicode_file.py", line 12, in TESTFN_UNICODE.encode(TESTFN_ENCODING) UnicodeEncodeError: 'mbcs' codec can't encode characters in position 0--1: invalid characte

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Hirokazu Yamamoto added the comment: How about TESTFN_UNICODE (test_unicode_file) issue? Should I reopen this entry or invalid? -- ___ Python tracker ___

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

STINNER Victor added the comment: > With r84666, Python uses "-\u5171\u6709\u3055\u308c\u308b" > suffix for TESTFN_UNENCODABLE. Backported to 3.1 as r84668. I don't want to patch Python 2.x (its unicode support is lower and the code is too different than Python3) and so I close the issue. -

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Hirokazu Yamamoto added the comment: Thank you for the fix. > 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. I won't. ;-) Sorry, that was not compliant. I just thought it's interesting

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Changes by STINNER Victor : Removed file: http://bugs.python.org/file18823/find_unencode_filename.py ___ Python tracker ___ ___ Python-bugs-lis

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

STINNER Victor added the comment: > "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

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Hirokazu Yamamoto added the comment: I also confirmed '\u0363' can be used as filename. "dir" command cannot print filename correctly, though. E:\python-dev\foo のディレクトリ 2010/09/10 19:44 . 2010/09/10 19:44 .. 2010/09/10 19:443 ͣ

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Hirokazu Yamamoto added the comment: Thank you for a reply. > u'\u2661' is encodable to cp949 Doh! I can imagine it's difficult to find out such character. ;-) -- ___ Python tracker __

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

STINNER Victor added the comment: See also #9820. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

STINNER Victor added the comment: > WARNING: The filename '@test_464_tmp-共有される' CAN be encoded > by (...) cp932 We should find character not encodable in any Windows code page, but accepted as filenames. > characters like "\u2661" or "\u2668" (...) mbcs uses "ANSI" code pages: cp1250..cp125

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Changes by Amaury Forgeot d'Arc : -- assignee: -> haypo nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

Hirokazu Yamamoto added the comment: And one little thing. I noticed variable name varies in python2.x and python3.x. TESTFN_UNICODE_UNDECODEABLE (2.x) TESTFN_UNICODE_UNDECODABLE (3.x) I think 2.x should be unified into 3.x name. Thanks. -- ___ Pyt

[issue9819] TESTFN_UNICODE and TESTFN_UNDECODABLE

New submission from Hirokazu Yamamoto : Hello. I noticed test suite reports WARNING every time. /// E:\python-dev>py3k -m test.regrtest test_os WARNING: The filename '@test_464_tmp-共有される' CAN be encoded by the filesyste m encoding (mbcs). Unicode