On 12/28/2011 11:49 AM, Armin Rigo wrote:
Hi Ned,
On Wed, Dec 28, 2011 at 15:34, Ned Batchelder wrote:
The problem with "bundling pypy's marshal.py" is that it pulls in a lot of
infrastructure modules, which bulks up the calling process.
Unsure what you mean. It seems to m
as possible, I propose simply bundling pypy's marshal.py
with the sandbox.
-- lahwran
On Tue, Dec 27, 2011 at 7:30 PM, Ned Batchelder wrote:
The sandbox uses pypy's own implementation of marshal. In
pypy/translator/sandbox/sandlib.py is this comment:
# Note: we use lib_pypy/marshal.
The sandbox uses pypy's own implementation of marshal. In
pypy/translator/sandbox/sandlib.py is this comment:
# Note: we use lib_pypy/marshal.py instead of the built-in marshal
# for two reasons. The built-in module could be made to segfault
# or be attackable in other ways by sending maliciou
I updated my sandbox work to yesterday's tip, and now I cannot import a
number of stdlib modules that used to work fine:
~/pypy> ./pypy/translator/sandbox/pypy_interact.py -q --heapsize=64m
pypy-c
Warning: cannot find your CPU L2 cache size in /proc/cpuinfo
'import site' failed
Py
Hi all,
I'm trying to use the PyPy sandbox to execute student code on a server.
I've got it all working, but it takes a few seconds to start the sandbox
process, so the response time from the server is poor. There are a few
issues:
1) The sandbox makes a lot of system calls as part of the
