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 gvanrossum
Recipients Justin Mayfield, gvanrossum, thehesiod, vstinner, yselivanov
Date 2015-11-12.04:59:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks, but I don't like the idea of that patch. It feels like a hack that makes it less likely that the issue occurs, but I don't feel we should rely on the callbacks being called before checking the selector again. There may be other reasons (perhaps a future modification to the code) why we might occasionally check the selector redundantly. IOW I think we should really ensure that all I/O callbacks are properly idempotent.
Date User Action Args
2015-11-12 04:59:42gvanrossumsetrecipients: + gvanrossum, vstinner, yselivanov, thehesiod, Justin Mayfield
2015-11-12 04:59:42gvanrossumsetmessageid: <>
2015-11-12 04:59:42gvanrossumlinkissue25593 messages
2015-11-12 04:59:42gvanrossumcreate