STINNER Victor victor.stin...@haypocalc.com added the comment:
No problems noted with a quick test of posixpath_darwin.patch
on 10.6 so looks good.
Ok thanks. Fix commited to 3.2 (r84866) and 2.7 (r84868). I kept my patch on
macpath (supports_unicode_filenames=True) because it is still
Ned Deily n...@acm.org added the comment:
No problems noted with a quick test of posixpath_darwin.patch on 10.6 so looks
good. It will get regression tested on more configurations sometime later.
--
___
Python tracker rep...@bugs.python.org
Changes by STINNER Victor victor.stin...@haypocalc.com:
Removed file: http://bugs.python.org/file18841/test_pep277.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue767645
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
r84784 sets os.path.supports_unicode_filenames to True on Mac OS X (macpath
module).
About test_supports_unicode_filenames.patch. test_unicode_listdir() is wrong:
os.listdir(str) always return str (see r84701). verify that the new
STINNER Victor victor.stin...@haypocalc.com added the comment:
I backported r84701 and r84784 to Python 2.7 (r84787).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue767645
___
Ned Deily n...@acm.org added the comment:
There seems to be some confusion about the macpath.py module. I'm not sure why
it even exists in Python 3. Note it has to do with obsolete Classic
MacOS-style paths (colon-separated paths) which are available on Mac OS X only
through deprecated
Martin v. Löwis mar...@v.loewis.de added the comment:
About Windows: supports_unicode_filenames is False if
sys.getwindowsversion().platform 2: win32s (0) or Windows 9x/ME
(1). I don't know win32s, but I know that Windows 9x/ME is not more
supported.
Win32s is long gone. It was an
Martin v. Löwis mar...@v.loewis.de added the comment:
I think that supports_unicode_filenames is still useful to check if
the filesystem API uses bytes (Linux, FreeBSD, Solaris, ...) or
characters (Mac OS X, Windows). Mac OS X is a special case because
the C API uses char* (byte string), but
STINNER Victor victor.stin...@haypocalc.com added the comment:
test_pep277.patch removes the usage of os.path.supports_unicode_filenames from
test_pep277: the test still pass on Debian Sid (Linux). Can someone test the
patch on Mac OS X, FreeBSD and Solaris (and maybe other POSIX/UNIX OSes)?
STINNER Victor victor.stin...@haypocalc.com added the comment:
Oops, forget test_pep277.patch: I misunderstood r81149 (new way to detect if
the filesystem supports unicode or not). test_pep277 fails with my patch on
Linux with LC_CTYPE=C.
--
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
r84701 fixes supports_unicode_filenames's definition in Python 3.2 (and r84702
in Python 3.1): os.listdir(str) now always return unicode filenames (including
non-ascii characters).
--
STINNER Victor victor.stin...@haypocalc.com added the comment:
Maybe os.path.supports_unicode_filenames should be deprecated.
The doc currently says:
True if arbitrary Unicode strings can be used as file names
(within limitations imposed by the file system), and if os.listdir()
returns
Mark Lawrence breamore...@yahoo.co.uk added the comment:
There are at least three messages stating that
os.path.supports_unicode_filenames should go so can someone please provide a
definitive statement regarding its future.
--
nosy: +BreamoreBoy
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue767645
___
___
Python-bugs-list mailing
Changes by Florent Xicluna florent.xicl...@gmail.com:
Removed file: http://bugs.python.org/file15842/issue767645_test_pep277.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue767645
___
Florent Xicluna florent.xicl...@gmail.com added the comment:
With r78594, test_pep277 is active on all platforms having Unicode-friendly
filesystem encoding.
--
type: - behavior
___
Python tracker rep...@bugs.python.org
Changes by Florent Xicluna la...@yahoo.fr:
--
components: +Tests
stage: - patch review
versions: +Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue767645
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue767645
___
___
Changes by Brett Cannon br...@python.org:
--
nosy: -brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue767645
___
___
Python-bugs-list
Ezio Melotti ezio.melo...@gmail.com added the comment:
Maybe os.path.supports_unicode_filenames should be deprecated.
The doc currently says:
True if arbitrary Unicode strings can be used as file names (within
limitations imposed by the file system), and if os.listdir() returns Unicode
strings
R. David Murray rdmur...@bitdance.com added the comment:
In addition, whether or not true unicode filenames are supported really
depends, at least on Linux, on the *filesystem*, not on the OS (for some
definition of support). In other words, I think
os.path.supports_unicode_filenames is an
Florent Xicluna la...@yahoo.fr added the comment:
Additionally it filters out test_pep277 on some platforms.
But seemingly, it is not needed anymore with this patch.
--
nosy: +flox
resolution: later -
Added file: http://bugs.python.org/file15842/issue767645_test_pep277.py
Joe Amenta ament...@msu.edu added the comment:
If it is decided to keep supports_unicode_filenames, here is a patch for
test_os.py that verifies the value of supports_unicode_filenames against the
following line from the documentation:
True if arbitrary Unicode strings can be used as file
Changes by Christian Heimes:
--
priority: normal - low
versions: +Python 2.6 -Python 2.3
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue767645
___
24 matches
Mail list logo
