On 6/27/06, <b class="gmail_sendername">Scott David Daniels</b> <<a href="mailto:Scott.Daniels@acm.org">Scott.Daniels@acm.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Brett Cannon wrote:<br>> On 6/27/06, Jim Jewett <<a href="mailto:jimjjewett@gmail.com">jimjjewett@gmail.com</a>> wrote:<br>>> ...<br>>> Caps and current usage should also be available (though read-only)
<br>>> from python; it is quite sensible to spill some cache when getting too<br>>> close to your memory limit.<br>><br>> Yeah, being able to read your restrictions seems reasonable to do from an<br>> untrusted interpreter.
<br><br>Certainly in some cases I'd like to run a Python program that claims it<br>"plays nice" without its being able to see that it is in jail. Otherwise<br>I can't escalate my trust of the code based on old behavior (it might be
<br>nice only when the jailer is around). So, reading your restrictions is<br>a capability I'd like to be able to control.</blockquote><div><br>Sounds reasonable.<br><br>-Brett<br></div><br></div>