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, glyph, gvanrossum, neologix, pitrou, sbt, vstinner, yselivanov
Date 2015-02-04.16:48:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1423068515.85.0.820069078035.issue19017@psf.upfronthosting.co.za>
In-reply-to
Content
Guido wrote:
"This still leaves case (1), where the FD is already bad when we register it.  I am actually fine with sometimes raising and sometimes not; I don't want to pay the extra overhead of doing an fstat() or some other syscall just to verify that it is valid.  (Although this would make the argument about wanting to choose a selector class that doesn't make extra syscalls less compelling. :-)  And neither do I want to ignore the error in register() and pretend success."

The asyncio has a debug mode which can execute expensive checks. These checks would not be acceptable in release mode since they are an impact on performances. In debug mode, asyncio can explicitly call fstat() before calling selector.register() or selector.modify().

This solution may be suggested in the documentation if someone wants a portable behaviour for all selector.
History
Date User Action Args
2015-02-04 16:48:35vstinnersetrecipients: + vstinner, gvanrossum, pitrou, giampaolo.rodola, glyph, neologix, sbt, yselivanov
2015-02-04 16:48:35vstinnersetmessageid: <1423068515.85.0.820069078035.issue19017@psf.upfronthosting.co.za>
2015-02-04 16:48:35vstinnerlinkissue19017 messages
2015-02-04 16:48:35vstinnercreate