[pypy-svn] r59699 - pypy/extradoc/talk/pycon2009

fijal at codespeak.net fijal at codespeak.net
Mon Nov 3 22:11:30 CET 2008


Author: fijal
Date: Mon Nov  3 22:11:30 2008
New Revision: 59699

Modified:
   pypy/extradoc/talk/pycon2009/pypy-sandbox.txt
Log:
leave my XXX


Modified: pypy/extradoc/talk/pycon2009/pypy-sandbox.txt
==============================================================================
--- pypy/extradoc/talk/pycon2009/pypy-sandbox.txt	(original)
+++ pypy/extradoc/talk/pycon2009/pypy-sandbox.txt	Mon Nov  3 22:11:30 2008
@@ -36,6 +36,9 @@
 program cannot easily detect that its file objects are in fact
 provided by another Python process. 
 
+XXX [fijal] important detail - we don't restrict python as a language at all
+XXX it also allows arbitrary access to *any* calls to C, not just files and IO
+
 Apart from Files and IO one can also RAM and CPU usage 
 which makes the PyPy approach probably the farthest 
 reaching one so far - providing a secure environment
@@ -49,6 +52,9 @@
 Basic familiarity with the project and/or reading up
 a bit on the pypy website is recommended. 
 
+XXX [fijal] why? I think that reader should not know about pypy
+XXX architecture in order to hear this talk
+
 simple slide outline:
 
 - Sandboxing movitation 



More information about the Pypy-commit mailing list