Le vendredi 09 septembre 2005 à 23:09 +1000, Neil Hodgson a écrit : > Antoine Pitrou: > > > As for seamless unicode support, there are also problems sometimes with > > filenames and filepaths: see e.g. > > https://sourceforge.net/tracker/?func=detail&aid=1283895&group_id=5470&atid=105470 > > This bug report is using byte string arguments causing byte string > processing rather than unicode calls with unicode processing. Windows > code that may encounter file paths outside the default locale should > stick to unicode for paths. Try converting os.curdir to unicode before > calling other functions: > > os.path.abspath(unicode(os.curdir)) I don't have a Windows machine at hand right now to test it, but, even if this solution works, it breaks the principle of least astonishment: os.path.abspath() should do the Right Thing regardless of what the current locale is. Regards Antoine.
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