Message 223227 - Python tracker

➜

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	vstinner
Recipients	giampaolo.rodola, gvanrossum, pitrou, python-dev, vstinner, yselivanov
Date	2014-07-16.15:53:35
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1405526015.87.0.605435731937.issue21645@psf.upfronthosting.co.za>
In-reply-to

Content
"A solution would be to schedule the callback in the event loop. Since Python 3.3, the C signal handler writes the signal number, which should be enough to find and schedule the Python callback." I wrote a patch implementing this idea to fix the issue: https://code.google.com/p/tulip/issues/detail?id=192

"A solution would be to schedule the callback in the event loop. Since Python 3.3, the C signal handler writes the signal number, which should be enough to find and schedule the Python callback."

I wrote a patch implementing this idea to fix the issue:
https://code.google.com/p/tulip/issues/detail?id=192

History
Date	User	Action	Args
2014-07-16 15:53:35	vstinner	set	recipients: + vstinner, gvanrossum, pitrou, giampaolo.rodola, python-dev, yselivanov
2014-07-16 15:53:35	vstinner	set	messageid: <1405526015.87.0.605435731937.issue21645@psf.upfronthosting.co.za>
2014-07-16 15:53:35	vstinner	link	issue21645 messages
2014-07-16 15:53:35	vstinner	create