[Python-Dev] doc for new restricted execution design for Python
brett at python.org
Sun Jun 25 22:08:32 CEST 2006
On 6/24/06, Bob Ippolito <bob at redivi.com> wrote:
> On Jun 24, 2006, at 2:46 AM, Nick Coghlan wrote:
> > Brett Cannon wrote:
> >> Yep. That API will be used directly in the changes to pymalloc and
> >> PyMem_*() macros (or at least the basic idea). It is not *only* for
> >> extension modules but for the core as well.
> >> Existing extension modules and existing C code in the Python
> >> interpreter
> >> have no idea of any PyXXX_ calls, so I don't understand how
> >> new API
> >> functions help here.
> >> The calls get added to pymalloc and PyMem_*() under the hood, so that
> >> existing extension modules use the memory check automatically
> >> without a
> >> change. The calls are just there in case some one has some random
> >> need
> >> to do their own malloc but still want to participate in the cap.
> >> Plus
> >> it helped me think everything through by giving everything I would
> >> need
> >> to change internally an API.
> > This confused me a bit, too. It might help if you annotated each of
> > the new
> > API's with who the expected callers were:
> > - trusted interpreter
> > - untrusted interpreter
> > - embedding application
> > - extension module
> Threading is definitely going to be an issue with multiple
> interpreters (restricted or otherwise)... for example, the PyGILState
> API probably wouldn't work anymore.
PyGILState won't work because there are multiple interpreters period, or
because of the introduced distinction of untrusted and trusted
interpreters? In other words, is this some new possible breakage, or is
this an issue with threads that has always existed with multiple
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev