➜

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 pitrou
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.16:45:56
SpamBayes Score 5.1786774e-05
Marked as misclassified No
Message-id <1272386891.3413.7.camel@localhost>
In-reply-to <1272375885.82.0.776192486581.issue7946@psf.upfronthosting.co.za>
Content 
> I stand corrected.   However, I'm going to have to think of a
> completely different approach for carrying out that functionality as I
> don't know how the take_gil() function is able to determine whether
> gil_last_holder has been deleted or not.

Please note take_gil() currently doesn't depend on the validity of the
pointer. gil_last_holder is just used as an opaque value, equivalent to
a thread id.
History
Date User Action Args
2010-04-27 16:45:59pitrousetrecipients: + pitrou, loewis, jhylton, gregory.p.smith, jcea, 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, dabeaz, mahmoudimus, aconrad, ysj.ray, neologix, thouis, donaldjeo
2010-04-27 16:45:56pitroulinkissue7946 messages
2010-04-27 16:45:56pitroucreate