Brett C. wrote: > Martin v. Löwis wrote: > >> Apparently, os.access was forgotten when the file system encoding >> was introduced in Python 2.2, and then it was again forgotten in >> PEP 277. >> >> I've now fixed it in the trunk (posixmodule.c:2.334), and I wonder >> whether this is a backport candidate. People who try to invoke >> os.access with a non-ASCII filename on non-NT+ systems will get >> a UnicodeError; with the patch, the operation will succeed >> (assuming the characters are all supported in the file system >> encoding). >> Should this be backported? +1; it's a bug, not a new feature. > If there was no other way to get os.access-like functionality, I would > say it should be backported. But since there are other ways to figure > out everything that os.access can tell you I say don't backport and > amend the docs to state it is not Unicode-aware. If one was adventurous > enough the docs could even include other ways to get the same info when > Unicode had to be used. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 08 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4