atomic operations in presence of multithreading

[Dave Brueck]

Paul Moore wrote:

> Dave Brueck <dave at pythonapocrypha.com> writes:
> 
> 
>>Yep, though I think the OP was mostly concerned with Python's
>>internals gettin messed up by unlocked multithreaded access, so he
>>doesn't have to be concerned about the above.
> 
> 
> I don't think that Python's internals can *ever* be messed up by
> unlocked multithreaded access - that's what the GIL is for.

Yeah, that was mentioned earlier:

"multiple threads can't corrupt the interpreter's internals (but a buggy 
C extension could)."

-Dave