Message8608

Author santa4nt
Recipients JonathanFeinberg, duffy151, fwierzbicki, irmen, santa4nt, zyasoft
Date 2014-06-08.19:22:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402255337.22.0.528733205264.issue1949@psf.upfronthosting.co.za>
In-reply-to
Content
Additionally, the "thread safety" of collections.deque in CPython is so only because it is implemented in C, so the GIL takes care that only one thread can call a method on a deque object at a given time, thereby ensuring that states are updated atomically within a single C function. Looking at CPython's implementation of deque, there is no additional concurrency constructs other than relying on the GIL.
History
Date User Action Args
2014-06-08 19:22:17santa4ntsetmessageid: <1402255337.22.0.528733205264.issue1949@psf.upfronthosting.co.za>
2014-06-08 19:22:17santa4ntsetrecipients: + santa4nt, fwierzbicki, irmen, zyasoft, JonathanFeinberg, duffy151
2014-06-08 19:22:17santa4ntlinkissue1949 messages
2014-06-08 19:22:17santa4ntcreate