http://cosmicpercolator.com/2013/03/12/atomic/ My God, it's full of stars! Mon, 27 May 2013 10:41:50 +0000 hourly 1 http://wordpress.com/ http://cosmicpercolator.com/2013/03/12/atomic/comment-page-1/#comment-303 Sat, 23 Mar 2013 16:14:09 +0000 http://cosmicpercolator.com/?p=3#comment-303 Yes, I should have mentioned that I had a conversation with Armin about this when he originally mentioned this on the PyPy blog. His patch was more ambitious, and involved not releasing the GIL even when explicitly doing so around blocking IO calls or other long duration calls.
The point of my proposal is to limit ourselves to merely stopping the volountary release of the GIL, but leaving explicit GIL release alone. This does not introduce any new deadlock cases.

]]> http://cosmicpercolator.com/2013/03/12/atomic/comment-page-1/#comment-302 Sat, 23 Mar 2013 15:44:12 +0000 http://cosmicpercolator.com/?p=3#comment-302 Armin Rigo suggested much the same thing as a hook for C extensions to play with when he first started working on his STM experiment, so it sounds good to me. (Armin ultimately rejected his own patch, http://bugs.python.org/issue12850, as not sufficiently interesting, but I think a cheap “threading.atomic()” context manager is interesting enough to be worthwhile, particularly since it allows certain data structure manipulation code to be made safe across multiple interpreter implementations)

]]>