Why does __builtins__ mean different things...
Terry Reedy
tjreedy at udel.edu
Thu Dec 20 22:22:22 EST 2007
More information about the Python-list mailing list
Thu Dec 20 22:22:22 EST 2007
- Previous message (by thread): Why does __builtins__ mean different things...
- Next message (by thread): Why does __builtins__ mean different things...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"James Stroud" <jstroud at mbi.ucla.edu> wrote in message news:fket7o$qr7$1 at daisy.noc.ucla.edu... | But....what the heck? You mean if I drop an s I get predictable behavior | and if I don't, I get unpredictable behavior? In 3.0, the __builtin__ module will be renamed 'builtins'. The internal __builtins__ variable most likely will continue to point to it (as it does now in main modules). Its purpose is to aid sandboxing by replacing the builtin module. If you are not doing that, ignore it.
- Previous message (by thread): Why does __builtins__ mean different things...
- Next message (by thread): Why does __builtins__ mean different things...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list