I've talked before about the speed advantage that Python builtins have . But speed isn't the only way that Pythonprivileges things written at the C level; as dict.setdefault() illustrates , Python makes a usefulatomicity guarantee for them that it does not make for methods writtenin Python itself.

Does this guarantee matter? I think that it does, because it issimultaneously useful and cheap. A concurrent program can avoid lockingwhen dealing with shared data built carefully from builtin types, andduplicating the effects

A comment on the previous entry about how builtins are atomic asked a really good question:

Is there actually a guarantee in CPython that they're atomic,or is that a side-effect of implementation?

There are two answers, at least in my opinion. The legalistic answeris that there is no guarantee at all, because there's nothing inthe documentation. But this is because the CPython documentationdoesn't talk about concurrency issues at all; even the thread moduledocumentation doesn't really say anything