[Python-Dev] doc for new restricted execution design for Python (original) (raw)
Brett Cannon brett at python.org
Fri Jul 7 19:04:55 CEST 2006
- Previous message: [Python-Dev] doc for new restricted execution design for Python
- Next message: [Python-Dev] In defense of Capabilities [was: doc for new restricted execution design for Python]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 7/7/06, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Another thing I perhaps should point out is that I'm proposing the separation of open() and file() for all code, not just restricted code. So it's not a matter of "crippling" file() specially for restricted code.
Well, that's fine with me since I use open() for opening all of my files anyway. But I don't know if people want to make 'file' the only built-in type who lacks a constructor on the type itself.
-Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060707/50760867/attachment.html
- Previous message: [Python-Dev] doc for new restricted execution design for Python
- Next message: [Python-Dev] In defense of Capabilities [was: doc for new restricted execution design for Python]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]