[pypy-dev] How to embed PyPy when there's no filesystem?

[tom at twhanson.com]

When I kick off the interctive sand-boxed version of PyPy I'm seeing it 
open a significant number of .py files. 
 
1) Am I correct in assuming that these are imports?
 
2) Can these be eliminated?  These opens are problematic in the 
absence of a file system. 
 
Thanks,
Tom

On Tue, 28 Apr 2015 22:50:57 +0200, Armin Rigo  wrote:

       Hi Tom,

On 28 April 2015 at 19:56,  wrote:
> Correction: " non-functional without the *peer* class
> VirtualizedSandboxedProc"

Modern PyPy versions try to get some environ variables, at least as
documented in rpython/doc/logging.rst. It makes the
do_ll_os__ll_os_getenv() method necessary (undefined methods cause the
subprocess to be aborted). Moreover, I'm sure that a PyPy in the
default configuration will try afterward to access the file system for
all its stdlib, which means it will call at least some of the other
methods too, starting from do_ll_os__ll_os_stat(). All these methods
happen to be in the VirtualizedSandboxedProc class. 

A bientôt,

Armin. 
_______________________________________________
pypy-dev mailing list
pypy-dev at python.org
https://mail.python.org/mailman/listinfo/pypy-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20150429/a5b8f211/attachment.html>