[issue5944] test_os failure on OS X, probably related to PEP 383

2020-03-16 Thread Matthias Braun
Matthias Braun added the comment: I believe my suggested pull request in https://bugs.python.org/issue39986 may solve this issue as a side effect because we no longer list the root directory but a temporary directory with controlled filenames. -- nosy: +Matthias Braun __

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Mark Dickinson
Mark Dickinson added the comment: Committed, r72359. -- resolution: accepted -> fixed status: open -> closed ___ Python tracker ___ __

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Martin v. Löwis
Martin v. Löwis added the comment: Fine with me, please apply. -- assignee: -> marketdickinson resolution: -> accepted ___ Python tracker ___ __

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Mark Dickinson
Mark Dickinson added the comment: > I think skipping the test entirely would be even better on Darwin. Sounds good to me! Here's a new (one-line) patch, using skipIf. -- Added file: http://bugs.python.org/file13899/issue5944_v2.patch ___ Python tra

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Martin v. Löwis
Martin v. Löwis added the comment: I think skipping the test entirely would be even better on Darwin. The test is really meant to pass only on systems that treat file names as uninterpreted byte sequences (as such, it may also fail on Linux if the file system driver enforces UTF-8). To skip it,

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Mark Dickinson
Mark Dickinson added the comment: Here's a patch that fixes the test failures for me. It's not ideal, because it no longer tests that on OS X, it's possible to open a file created with an invalid filename, using that same name. -- keywords: +patch Added file: http://bugs.python.org/f

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Mark Dickinson
Mark Dickinson added the comment: Even better: >>> for s in map(unicodedata.name, found): print(s) ... LATIN SMALL LETTER F LATIN SMALL LETTER O LATIN SMALL LETTER O LATIN SMALL LETTER O COMBINING DIAERESIS LATIN SMALL LETTER B LATIN SMALL LETTER A LATIN SMALL LETTER R >>> for s in map(unicode

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Mark Dickinson
Mark Dickinson added the comment: > The case where the letter looks the same (at least in my email) but is > apparently different may require some thought, too. In case it's useful, when I do a list(map(ord, ...)) on those two lookalike strings I get (where 'expected' comes from the explicit .

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread R. David Murray
R. David Murray added the comment: OS/X needs to be special cased in the tests, since it transforms the invalid filenames on write. And if I remember correctly older versions do something different...throw an error, maybe? The case where the letter looks the same (at least in my email) but is

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Mark Dickinson
Mark Dickinson added the comment: One other piece of information that may be relevant: Macintosh-4:py3k dickinsm$ echo $LANG en_US.UTF-8 If I unset the LANG environment variable then I get a different failure (see output below). I'll investigate this further and see if I can figure out what

[issue5944] test_os failure on OS X, probably related to PEP 383

2009-05-05 Thread Mark Dickinson
New submission from Mark Dickinson : I'm getting what looks like a PEP 383-related failure in test_os, on OS X 10.5.6. Here's the tail end of running Lib/test/test_os.py, on a standard non-debug build of py3k. test_setuid (__main__.PosixUidGidTests) ... ok test_listdir (__main__.Pep383Tests) .