> While trying to configure an in-package Python interpreter > I found that the interpreter still uses 'string.py' as > landmark for finding the standard library. Oops. > Since string.py is being depreciated, I think we should > consider a new landmark (such as os.py) or maybe even a > whole new strategy for finding the standard lib location. I don't see a need for a new strategy, but I'll gladly accept patches that look for os.py. Note that there are several versions of that code: Modules/getpath.c, PC/getpathp.c, PC/os2vacpp/getpathp.c. --Guido van Rossum (home page: http://www.python.org/~guido/)
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