On Thu, 23 Aug 2001, Tim Peters wrote:
> So I propose a new builtin module, _sysconsts. The underscore is to
> announce its obscure internal nature. I propose only to expose the CO_xxx
> #defines at the start, but of course others could be added.
Just a suggestion, but how about sys.consts? Like os.path, as in
sys.consts.CO_NESTED, sys.consts.CO_FUTURE_DIVISION, etc. So there's
only one new object in sys, and it can contain the weird internal stuff. :)
(Errr... the names are rather weird. CO_NESTED_SCOPES, CO_TRUE_DIVISION,
and CO_GENERATORS would be better. If i had my druthers it would be
CO_* constant FUTURE_* constant __future__ symbol
CO_NESTED_SCOPES FUTURE_NESTED_SCOPES nested_scopes
CO_GENERATORS FUTURE_GENERATORS generators
CO_TRUE_DIVISION FUTURE_TRUE_DIVISION true_division
instead. If CO_NESTED, why not CO_TRUE? If CO_GENERATORS_ALLOWED,
why not CO_NESTED_SCOPES_ALLOWED?)
Anyway.
Hmm, as a side thought, perhaps keywords and tokens should go here too
(sys.keywords, sys.tokens) instead of having to keep separate .py files
in sync with the interpreter core.
-- ?!ng
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