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 swapnil
Recipients amaury.forgeotdarc, anacrolix, docs@python, ncoghlan, nikratio, swapnil, verigak
Date 2010-09-21.04:38:58
SpamBayes Score 6.235528e-07
Marked as misclassified No
Message-id <1285043943.16.0.816529286647.issue6627@psf.upfronthosting.co.za>
In-reply-to
Content
Nick, the last statement,
"While this is correct for most purposes, it does mean that..."
can be simplified to, 
"It means...". 
I had to read it several times before I realized, there is no "not" after "does" :) 
BTW, since this particular arrangement of having a temporary thread state during the callback is particularly useful for ctypes (I cannot imagine any other usecase) and also it sort-of breaks things, a potential feature request could be to have consistent thread state during the lifetime of a C thread. I don't have much idea how to do that or whether it is even possible? Would anyone like to give a thought?
History
Date User Action Args
2010-09-21 04:39:03swapnilsetrecipients: + swapnil, amaury.forgeotdarc, ncoghlan, nikratio, verigak, anacrolix, docs@python
2010-09-21 04:39:03swapnilsetmessageid: <1285043943.16.0.816529286647.issue6627@psf.upfronthosting.co.za>
2010-09-21 04:39:01swapnillinkissue6627 messages
2010-09-21 04:38:59swapnilcreate