summary: a Path protocol
The discussion has ranged all over, so let me try to sum up: Name: __ospath__ Method or attribute? Method (implementations are of course free to pre-build and/or cache the value) Built-in? no, rather a function in pathlib - ospath() Add the method/attribute to str? Not necessary -- but if somebody else wants to do that part I am not opposed Expand the C API to have something like PyObject_Path()? Yes - and if I understood correctly this function will do the same as pathlib.ospath(), just at the C level? And what will its name be, exactly? -- ~Ethan~
Sorry, I don't have time to read the whole discussion. What is the problem with adding a __str__ to pathlib? Victor
On Fri, Apr 8, 2016 at 4:35 PM, Victor Stinner
Sorry, I don't have time to read the whole discussion. What is the problem with adding a __str__ to pathlib?
Victor
Everything else has __str__ too, so you run the risk of open(["Hello", "World"], "w") working and doing something weird. Or of passing an open file object to something that was expecting a file name, and having *that* work too. Calling str(p) on something that ought to be either a Path or a string should raise an exception if given something else. ChrisA
participants (3)
-
Chris Angelico
-
Ethan Furman
-
Victor Stinner