Here is a far more baffling one: Not Implemented: sandboxing for external function 'pypy_jit_depthmap_add'
That's certainly not something I would expect the controller process to implement. It seems to happen after a bunch of repetitive commands (when I suppose JIT is kicking in). BTW, I did not run into either of these issues with a build from a year ago, around commit 72100. If anyone can suggest what I might be doing wrong, I would greatly appreciate. Dmitry On Mon, Jun 8, 2015 at 6:31 PM, Dmitry Sagalovskiy <dmi...@getgrist.com> wrote: > Hi! > > I am getting this error from the sandbox: > > Not Implemented: sandboxing for external function 'fcntl' > > I am using a custom controller process, and getting this in fdopen > (pypy_interact bombs on something else before it gets to that point). After > much digging, I think this is due to _check_fd_mode function in > rpython/rlib/streamio.py. In sandbox mode, I think there is little use for > this check, but since it's there, I need some workaround. Does anyone have > recommendations? > > More generally, my team needs to decide if we can rely on the pypy sandbox > to use in our product. It seems brilliantly designed, fast, and overall > impressive. But there are these gaps in missing sandbox wrappers (there are > others too, fcntl is just one that I don't know how to avoid). And I > noticed some code that indicates that it is not supported on Windows -- is > that the case? > > What are the sandbox's prospects, within the larger future of pypy? > > Dmitry > >
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
