[Python-Dev] Defining a path protocol (original) (raw)
Brett Cannon brett at python.org
Wed Apr 6 16:55:41 EDT 2016
- Previous message (by thread): [Python-Dev] Defining a path protocol
- Next message (by thread): [Python-Dev] Defining a path protocol
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 6 Apr 2016 at 13:54 Sven R. Kunze <srkunze at mail.de> wrote:
On 06.04.2016 22:28, Brett Cannon wrote:
On Wed, 6 Apr 2016 at 13:20 Sven R. Kunze < <srkunze at mail.de> srkunze at mail.de> wrote:
What about filepath Can be a directory as well (and you could argue semantics of file system inodes, beginners won't know the subtlety and/or wonder where dirpath is). Good point. Well, then fspath for me. I knew instantly what it means especially considering btrfs, ntfs, xfs, zfs, etc. Furthermore, we MIGHT later want some URI support, so I don't know off the top of my head if there's a difference between fspath and urlpath but better separate it now. Later we can re-merge then if necessary.
There's a difference as a URL represents something different than a file system path (URI doesn't necessarily). Plus the serialized format would be different, etc. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160406/6edcdab4/attachment.html>
- Previous message (by thread): [Python-Dev] Defining a path protocol
- Next message (by thread): [Python-Dev] Defining a path protocol
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]