Showing content from http://mail.python.org/pipermail/python-dev/attachments/20071128/78c86ba8/attachment.htm below:
(The lurker awakes...)<div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">> If not that I suggest something like __inject_builtins__. This
<br>> implies it's a command to eval/exec, and doesn't necessarily reflect<br>> your current builtins (which are canonically accessible as an<br>> attribute of your frame.)<br><br></div>You're misunderstanding the reason why __builtins__ exists at all. It
<br>is used *everywhere* as the root namespace, not just as a special case<br>to inject different builtins.<br><br>ATM I'm torn between __root__ and __python__.</blockquote><div><br class="webkit-block-placeholder"></div>
<div>Something with the word "global" speaks to it's real effect, except that the word already has an established meaning in Python as being 'global to the module level', and modifying __builtins__ lets you be "global to the entire universe of that instance"
</div><div><br class="webkit-block-placeholder"></div><div>So I would humbly suggest __universal__. The names within are available everywhere. 'root' speaks to me too much of trees, and while namespaces may be tree-like, __root__ alone doesn't say "root namespace"... and __root_namespace__ is long.
</div><div><br class="webkit-block-placeholder"></div><div>(Then again, long for a feature that should only be used with care isn't a bad thing)</div><div><br class="webkit-block-placeholder"></div><div>--Stephen</div>
</div></div>
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