[Python-ideas] Fwd: Concurrent safety?

Jim Jewett jimjjewett at gmail.com
Fri Nov 4 06:18:52 CET 2011


On Thu, Nov 3, 2011 at 12:35 AM, Stephen J. Turnbull <stephen at xemacs.org> wrote:

> As for "wrapped C libraries", I'm having trouble imagining what you're
> talking about.

C code (currently) can create or modify python objects using a C
pointer, instead of python access.  That is the biggest barrier to a
tracing (as opposed to reference-counting) garbage collector.  It is
also a problem for security sandboxes (though they can just ban C
extensions).  Most relevant here, C extensions can also bypass any
locks or protections put in place for concurrency.

-jJ



More information about the Python-ideas mailing list