(1) What is the advantage of module Path vs just turning os.path into a class? (except that people already import from os.path, so I suppose it would need to be os.Path) (2) It sounds like quite a few stdlib calls will be both deprecated and wrapped. Having a new stdlib module rely on deprecated features leaves a bad taste. Perhaps move the functionality to the Path class and then forward from the current (about to be deprecated) modules? -jJ
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