➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dabeaz
Recipients DazWorrall, aconrad, alex, andrix, brian.curtin, carljm, coderanger, cool-RR, dabeaz, djc, donaldjeo, durin42, eric.araujo, eric.smith, flox, gregory.p.smith, jcea, jhylton, karld, kevinwatters, konryd, larry, loewis, mahmoudimus, movement, neologix, nirai, pitrou, rcohen, rh0dium, tarek, thouis, ysj.ray
Date 2010-04-27.12:44:44
SpamBayes Score 7.356624e-05
Marked as misclassified No
Message-id <1272372286.19.0.963204766455.issue7946@psf.upfronthosting.co.za>
In-reply-to
Content 
That second access of gil_last_holder->cpu_bound is safe because that block of code is never entered unless some other thread currently holds the GIL.   If a thread holds the GIL, then gil_last_holder is guaranteed to have a valid value.
History
Date User Action Args
2010-04-27 12:44:46dabeazsetrecipients: + dabeaz, loewis, jhylton, gregory.p.smith, jcea, pitrou, movement, larry, eric.smith, kevinwatters, tarek, djc, karld, carljm, coderanger, durin42, eric.araujo, nirai, alex, andrix, konryd, brian.curtin, flox, DazWorrall, cool-RR, rh0dium, rcohen, mahmoudimus, aconrad, ysj.ray, neologix, thouis, donaldjeo
2010-04-27 12:44:46dabeazsetmessageid: <1272372286.19.0.963204766455.issue7946@psf.upfronthosting.co.za>
2010-04-27 12:44:45dabeazlinkissue7946 messages
2010-04-27 12:44:45dabeazcreate