[Python] '__builtin__' vs. __builtins__
Jun 17, 2002 at 12:47 pm
Why is the '__builtin__' module available under the __builtins__ name?
By what's the logic one is supposed to remember it? (If I do remember
that it's different I would still confuse which is what...)
Beni Cherniavsky <cben at tx.technion.ac.il>
: forget about __builtins__; it's an implementation detail. if you need to explicitly refer to stuff in the built-in namespace, *always* import the __builtin__ module. never use __builtins__ in your code.
: In article , Beni Cherniavksy wrote: My paraphrase of what Tim Peters said the last time this came up: Main reason is to avoid getting flooded with output when calling ``vars()`` in interactive mode. (From my upcoming OSCON tutorial.) -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ Project Vote Smart: http://www.vote-smart.org/
__builtin__ vs __builtins__?
Peculiar Behaviour of __builtins__
Why aren't copy and deepcopy in __builtins__?
Overriding the >> builtin
__import__ returns module without it's attributes?
__buitins__ key added during eval()
why? __builtins__ key added from eval
__builtins__ magic behavior
question about python statements
1 of 3
Jun 17, '02 at 12:47p
Jun 17, '02 at 8:34p
3 users in discussion
Beni Cherniavksy (1)
Fredrik Lundh (1)
Groups & Organizations
site design / logo © 2022 Grokbase