Phillip J. Eby wrote: > At 09:49 AM 10/25/2006 -0700, Talin wrote: >> Having done a path library myself (in C++, for our code base at work), >> the trickiest part is getting the Windows path manipulations right, and >> fitting them into a model that allows writing of platform-agnostic code. >> This is especially vexing when you realize that its often useful to >> manipulate unix-style paths even when running under Win32 and vice >> versa. A prime example is that I have a lot of Python code at work that >> manipulates Perforce client specs files. The path specifications in >> these files are platform-agnostic, and use forward slashes regardless of >> the host platform, so "os.path.normpath" doesn't do the right thing >> for me. > > You probably want to use the posixpath module directly in that case, > though perhaps you've already discovered that. Never heard of it. Its not in the standard library, is it? I don't see it in the table of contents or the index.
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