[Python-Dev] Defining a path protocol (original) (raw)
Chris Barker chris.barker at noaa.gov
Thu Apr 7 12:56:21 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 Thu, Apr 7, 2016 at 12:00 AM, INADA Naoki <songofacandy at gmail.com> wrote:
I feel adding protocol only for path is bit over engineering. So I'm -0.5 on adding fspath. I'm +1 on adding general protocol for coerce to string like index.
isn't str the protocol for "coerce to string" ?
index is a protocol for "coerce to an integer that can be used as an index", which is like fspath would be "coerce to a string that can be used as a path"
the whole point is that str will "work" with virtually anything -- whether it can reasonably be used as a path or not. I'm not sure that's a problem, but if it is, then that's what this new protocol is trying to solve, just like Index enforces that only things that are intended to be used as indexes will work.
-CHB
--
Christopher Barker, Ph.D. Oceanographer
Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker at noaa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160407/e834e242/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 ]