Brett Cannon brett at python.org
Wed Mar 7 20:16:02 CET 2012

• Previous message: [Python-Dev] Adding a builtins parameter to eval(), exec() and __import__().
• Next message: [Python-Dev] Adding a builtins parameter to eval(), exec() and __import__().
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Wed, Mar 7, 2012 at 10:56, Benjamin Peterson <benjamin at python.org> wrote:

> 2012/3/7 Mark Shannon <mark at hotpy.org>:
> > Currently, it is impossible to allow one function access to sensitive
> > functions like open(), while denying it to others, as any code can then
> > get the builtins of another function via f.__globals__['builtins__'].
> > Separating builtins from globals could solve this.
>
> I like this idea. We could finally kill __builtins__, too, which has
> often been confusing for people.


I like it as well. It's a mess right now to try to grab the __import__()
implementation and this would actually help clarify import semantics by
saying that __import__() for any chained imports comes from __import__()s
locals, globals, or builtins arguments (in that order) or from the builtins
module itself (i.e. tstate->builtins).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120307/3d47246c/attachment.html>

---

• Previous message: [Python-Dev] Adding a builtins parameter to eval(), exec() and __import__().
• Next message: [Python-Dev] Adding a builtins parameter to eval(), exec() and __import__().
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list