try to limit language features considered “unsafe”. Instead we replace all
calls to external libraries (C or platform) with a stub that communicates
with an external process handling the policy.</p>
<p>Please be aware that it is a <strong>prototype</strong> only. It needs work to become
more complete, and you are welcome to help.</p>
<tableclass="docutils">
<colgroup>
<colwidth="100%"/>
</colgroup>
<tbodyvalign="top">
<tr><td><strong>Please be aware that it is a prototype only.</strong><em>It needs work to become
more complete, and you are welcome to help. In particular, almost none
of the extension modules work (not even</em><ttclass="docutils literal">time</tt><em>), and</em><ttclass="docutils literal">pypy_interact</tt>
<em>is merely a demo. Also, a more complete system would include a way
to do the same as</em><ttclass="docutils literal">pypy_interact</tt><em>from other languages than Python,
to embed a sandboxed interpreter inside programs written in other
languages.</em></td>
</tr>
</tbody>
</table>
<p>To run the sandboxed process, you need to get the full sources and
build <ttclass="docutils literal"><spanclass="pre">pypy-sandbox</span></tt> from it (see <aclass="reference external"href="download.html#building-from-source">Building from source</a>). These
instructions give you a <ttclass="docutils literal"><spanclass="pre">pypy-c</span></tt> that you should rename to