Ethan Furman ethan at stoneleaf.us
Wed Apr 6 16:07:54 EDT 2016

• Previous message (by thread): [Python-Dev] Defining a path protocol
• Next message (by thread): [Python-Dev] Defining a path protocol (was: When should pathlib stop being provisional?)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On 04/06/2016 12:32 PM, Paul Moore wrote:

> But I'm not one of the people who disliked using .path, so I'm
> probably not best placed to judge. It would be good if someone who
> *does* feel strongly could explain why fspath(pathobj) is better than
> pathobj.path.

fspath() would be useful because you can pass it a str or a Path and get 
a str back (or an exception if you pass the wrong thing in).

Just like with Path you can pass a str or a Path get a Path back (or an 
exception if ...).

--
--
~Ethan~

---

• Previous message (by thread): [Python-Dev] Defining a path protocol
• Next message (by thread): [Python-Dev] Defining a path protocol (was: When should pathlib stop being provisional?)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list