Chris Barker - NOAA Federal wrote: > But fspath(), if it exists, would call __fspath__ on an arbitrary > object, and create a new string -- not a new Path. That may be > confusing... Maybe something like fspathstr/__fspathstr__ would be better? -- Greg