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 gvanrossum, neologix, vstinner
Date 2013-11-01.00:18:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383265087.38.0.833995871291.issue19465@psf.upfronthosting.co.za>
In-reply-to
Content
> It still seems to me that this is pretty atypical use of selectors

I already implemented something similar to subprocess.Popen.communicate() when I was working on old Python versions without the timeout parameter of communicate().
http://ufwi.org/projects/edw-svn/repository/revisions/master/entry/trunk/src/nucentral/nucentral/common/process.py#L222

IMO calling select with a few file descriptors (between 1 and 3) and destroying quickly the "selector" is no a rare use case.

If I would port my code to selectors, I don't want to rewrite it to keep the selector alive longer, just because selectors force me to use the super-powerful fast epoll/kqueue selector.

(To be honest, I will probably not notice any performance impact. But I like reducing the number of syscalls, not the opposite :-))
History
Date User Action Args
2013-11-01 00:18:07vstinnersetrecipients: + vstinner, gvanrossum, neologix
2013-11-01 00:18:07vstinnersetmessageid: <1383265087.38.0.833995871291.issue19465@psf.upfronthosting.co.za>
2013-11-01 00:18:07vstinnerlinkissue19465 messages
2013-11-01 00:18:07vstinnercreate