glyph at divmod.com wrote: > I am not addressing this message to the py3k list because its general > message of extreme conservatism on new features is more applicable to > python-dev. However, py3k designers might also take note: if py3k is > going to do something in this area and drop support for the "legacy" > os.path, it would be good to choose something that is known to work and > have few gotchas, rather than just choosing the devil we don't know over > the devil we do. The weaknesses of os.path are at least well-understood. that's another reason why a new design might as well be defined in terms of the old design -- especially if the main goal is call-site convenience, rather than fancy new algorithms. </F>
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