[Python-ideas] Working with Path objects: p-strings?

[Sven R. Kunze]

On 29.03.2016 23:57, Paul Moore wrote:
> On 29 March 2016 at 22:00, Sven R. Kunze <srkunze at mail.de> wrote:
>> However, something that I cannot leave uncommented is "suboptimal
>> representation for paths". What would your optimal representation for paths
>> look like? I cannot believe that the current representation is so bad and
>> has been for so long and nobody, really nobody, has anything done about it.
> Well, pathlib.Path :-)
>
> The point here is that C's char* representation is a serialisation of
> a path object, just like 123 is a serialisation of an integer object.
> We don't object to having to convert user input to a string if we need
> to, why object to having to convert it to a Path if appropriate?

I think there is a misunderstanding here. Let me quote myself:

'''I think most "practicality beats purity" folks don't want that 
either. They are just bloody lazy. They actually want the benefits of 
both, the pure datastructure with its convenience methods and the dirty 
str-like thing with its convenience methods.'''

The desire is not "str vs. Path"; its "Path + str". (at least from what 
I can tell)


Best,
Sven