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 fdirosa
Recipients Rhamphoryncus, fdirosa, grahamd, nnorwitz, timbishop, vslavik
Date 2008-07-21.15:42:08
SpamBayes Score 0.0022457512
Marked as misclassified No
Message-id <1216654929.98.0.137565237681.issue1758146@psf.upfronthosting.co.za>
In-reply-to
Content
By the way.  I switched to using the GIL functions on the main 
interpreter and everything works great now.  It is a better solution to 
use the GIL functions because I also had my own code that prevented 
dead lock from occuring when a python script calls back into the 
extension module that ends up calling PyEval_Acquire again (deadlock) 
even though it is the same thread.  Now with the GIL functions I don't 
need that code.  It is a good feature but it broke my previous 
implementation and it is not obvious why.
History
Date User Action Args
2008-07-21 15:42:10fdirosasetspambayes_score: 0.00224575 -> 0.0022457512
recipients: + fdirosa, nnorwitz, Rhamphoryncus, timbishop, vslavik, grahamd
2008-07-21 15:42:10fdirosasetspambayes_score: 0.00224575 -> 0.00224575
messageid: <1216654929.98.0.137565237681.issue1758146@psf.upfronthosting.co.za>
2008-07-21 15:42:09fdirosalinkissue1758146 messages
2008-07-21 15:42:08fdirosacreate