At 08:19 PM 6/26/2005 +0100, Michael Hoffman wrote: >On Sun, 26 Jun 2005, Phillip J. Eby wrote: > > > * drop getcwd(); it makes no sense on a path instance > >Personally I use path.getcwd() as a class method all the time. It >makes as much sense as fromkeys() does on a dict instance, which is >technically possible but non-sensical. It's also duplication with os.path; I'm -1 on creating a new staticmethod for it. >Reinhold Birkenfeld wrote: > > > One more issue is open: the one of naming. As "path" is already the > > name of a module, what would the new object be called to avoid > > confusion? pathobj? objpath? Path? > >I would argue for Path. It fits with the recent cases of: > >from sets import Set >from decimal import Decimal I like it too, as a class in the os module.
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