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 giampaolo.rodola
Recipients Erez.Sh, William.Edwards, asksol, danken, dmalcolm, giampaolo.rodola, jnoller, pitrou, sbt, synapse, vstinner
Date 2012-10-22.18:31:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350930685.73.0.415118322872.issue10527@psf.upfronthosting.co.za>
In-reply-to
Content
Using poll() by default is controversial for 2 reasons, I think:

#1 - a certain slowdown is likely to be introduced (I'll measure it)

#2 - current wait() implementation allows to specify a list of file descriptors and/or Connections objects. 
select() can deal with both while poll() does not (it will return a list of integers rather than a list of Connection instances).

I'm not sure how "public" multiprocessing.connection.wait() is considered and how much backward compatibility should matter in this case.


> behaviour might change subtly when the fd becomes > 512

What do you mean?
History
Date User Action Args
2012-10-22 18:31:25giampaolo.rodolasetrecipients: + giampaolo.rodola, pitrou, vstinner, jnoller, synapse, asksol, dmalcolm, danken, Erez.Sh, sbt, William.Edwards
2012-10-22 18:31:25giampaolo.rodolasetmessageid: <1350930685.73.0.415118322872.issue10527@psf.upfronthosting.co.za>
2012-10-22 18:31:25giampaolo.rodolalinkissue10527 messages
2012-10-22 18:31:25giampaolo.rodolacreate