[Python-Dev] PEP 355 status (original) (raw)
Talin talin at acm.org
Wed Oct 25 19:16:48 CEST 2006
- Previous message: [Python-Dev] PEP 355 status
- Next message: [Python-Dev] PEP 355 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
- Previous message: [Python-Dev] PEP 355 status
- Next message: [Python-Dev] PEP 355 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]