Message 176569 - 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	pitrou
Recipients	amaury.forgeotdarc, felipecruz, jcea, pitrou
Date	2012-11-28.19:24:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1354130683.99.0.726420985907.issue16565@psf.upfronthosting.co.za>
In-reply-to

Content
I just took a look at https://github.com/felipecruz/pyaio/commit/127372ba0a6dbca4045256dcd653789ee35f6a78 and it looks a bit silly to me: if the completion handler is called in a separate thread, then the completion handler can just take the GIL and put the results in a regular Python queue. In short, using signals for any kind of high-speed I/O sounds completely archaic to me.

I just took a look at https://github.com/felipecruz/pyaio/commit/127372ba0a6dbca4045256dcd653789ee35f6a78 and it looks a bit silly to me: if the completion handler is called in a separate thread, then the completion handler can just take the GIL and put the results in a regular Python queue.

In short, using signals for any kind of high-speed I/O sounds completely archaic to me.

History
Date	User	Action	Args
2012-11-28 19:24:44	pitrou	set	recipients: + pitrou, jcea, amaury.forgeotdarc, felipecruz
2012-11-28 19:24:43	pitrou	set	messageid: <1354130683.99.0.726420985907.issue16565@psf.upfronthosting.co.za>
2012-11-28 19:24:43	pitrou	link	issue16565 messages
2012-11-28 19:24:42	pitrou	create