On Fri, 8 Apr 2016 at 11:13 Ethan Furman <ethan at stoneleaf.us> wrote: > On 04/08/2016 10:46 AM, Koos Zevenhoven wrote: > > On Fri, Apr 8, 2016 at 7:42 PM, Chris Barker wrote: > >> On Fri, Apr 8, 2016 at 9:02 AM, Koos Zevenhoven wrote: > > >>> I'm still thinking a little bit about 'pathname', which to me sounds > >>> more like a string than fspath does. > >> > >> > >> I like that a lot - or even "__pathstr__" or "__pathstring__" > >> after all, we're making a big deal out of the fact that a path is > >> *not a string*, but rather a string is a *representation* (or > >> serialization) of a path. > > That's a decent point. > > So the plausible choices are, I think: > > - __fspath__ # File System Path -- possible confusion with Path > +1 > > - __fsstr__ # File System String > -1 Looks like a cat walked across my keyboard or someone trying to come up with a trendy startup name. > > - __fspathstr__ # File System Path String -- zero ambiguity, but > # what a mouthful > -1 See above. I personally still like __ospath__ as well. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160408/56476647/attachment.html>
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