Guido van Rossum wrote: >>BTW, this reminds me of the old idea to move that standard >>lib into a package, eg. 'python'... >> >>from python import time. > > > Maybe in Python 3000. In 2.x, I think rearranging the standard > library will just cause more upheaval without much benefits. > > >>We should at least reserve such a name RSN so that we don't >>run into problems later on. > > > I can guarantee you that that name won't be used as a standard Python > module or package name any time soon. If someone creates a 3rd party > package or module named 'python' I'd question their sanity. :-) How about adding python.py: __path__ = ['.'] This would not only reserve the name in the global namespace, but also enable applications to start using 'from python import x' now without much fuzz. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH _______________________________________________________________________ eGenix.com -- Makers of the Python mx Extensions: mxDateTime,mxODBC,... Python Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
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