Mike Orr wrote: > There's something that bothers me about putting the path in an > attribute rather than subclassing tuple. [...] > How do you do slicing and joining? If Path subclasses object, it > could be done there like in the first example. But if Path subclasses > string, that API is taken: I think Path should neither subclass string nor tuple. It might behave like a string or a tuple, but it shouldn't subclass, as that unnecessarily constraints the implementation strategy. In particular, it shouldn't subclass str, as you then could not represent Unicode file names in a reasonable way anymore. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4