A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2007-November/075437.html below:

[Python-Dev] [poll] New name for __builtins__

[Python-Dev] [poll] New name for __builtins__Nick Coghlan ncoghlan at gmail.com
Thu Nov 29 12:15:12 CET 2007
Given that the *effect* of __builtins__ is to make the contents of the 
__builtin__ module implicitly available in every module's global 
namespace, why not call it __implicit__?

I really don't like all of these __root__ inspired names, because 
__builtin__ isn't the root of any Python hierarchy that I know of.

 >>> import sys
 >>> import __builtin__
 >>> __builtin__.sys
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'sys'

The builtin namespace doesn't know anything about other modules, the 
current module's global namespace, the current function's local 
variables, or much of anything really. To me, the concept of "root" in a 
computing sense implies a node from which you can reach every other node 
- from the root of the filesystem you can get to every other directory, 
as the root user you can access any other account, etc. To those that 
like these names, what do you consider __root__ to be the root of?

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
             http://www.boredomandlaziness.org
More information about the Python-Dev mailing list

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