➜

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 ncoghlan
Recipients anacrolix, ncoghlan, nikratio, swapnil, verigak
Date 2010-09-17.15:08:09
SpamBayes Score 8.178306e-05
Marked as misclassified No
Message-id <1284736096.65.0.879743692532.issue6627@psf.upfronthosting.co.za>
In-reply-to
Content 
Swapnil's analysis looks correct to me - there are certain rules you have to follow before calling back into the Python interpreter core. If you don't follow them, the behaviour you will get is completely undefined.

If the problem still occurs even when the C thread is correctly initialised for calling into the Python C API then this issue can be reopened.
History
Date User Action Args
2010-09-17 15:08:16ncoghlansetrecipients: + ncoghlan, nikratio, verigak, swapnil, anacrolix
2010-09-17 15:08:16ncoghlansetmessageid: <1284736096.65.0.879743692532.issue6627@psf.upfronthosting.co.za>
2010-09-17 15:08:10ncoghlanlinkissue6627 messages
2010-09-17 15:08:10ncoghlancreate