> >>>>> "KY" == Ka-Ping Yee <ping@lfw.org> writes: > > KY> Just a suggestion, but how about sys.consts? Like os.path, as > KY> in sys.consts.CO_NESTED, sys.consts.CO_FUTURE_DIVISION, etc. > KY> So there's only one new object in sys, and it can contain the > KY> weird internal stuff. :) > > +1. It's much better to qualify them in a subpackage or object than > put them in sys's top level namespace. +0. It's the better solution but I bet it's more work to code it than _sysconst. I'm not volunteering, and I want Tim to have time to help with the type/class unification, which is behind schedule. --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