12 Oct
2012
12 Oct
'12
11:37 a.m.
Nick Coghlan wrote:
Making "+" and "Path.join" mean something different from what they mean when called on strings is, in the specific case of a path representation, far too likely to lead to data corruption bugs for us to be happy with allowing it in the standard library. This is one I think Jason Orendorff's original path.py got right, which is why my current preference is "just copy path.py and use / and Path.joinpath".
Okay, that makes sense.
I think we should settle on one of the possibilities that does /not/ duplicate the word 'path', however. That's one of those things that drives me nuts. ;) (It's a Path object -- of /course/ it's joining path stuff!)
~Ethan~