On 22/04/2009 14:20, glyph at divmod.com wrote: > -1. On UNIX, character data is not sufficient to represent paths. We > must, must, must continue to have a simple bytes interface to these > APIs. Covering it up in layers of obscure encoding hacks will not make > the problem go away, it will just make it harder to understand. As a hg developer, I have to concur. Keeping bytes-based APIs intact would make porting hg to py3k much, much easier. You may be able to imagine that dealing with paths correctly cross-platform on a VCS is a major PITA, and py3k is currently not helping the situation. Cheers, Dirkjan
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