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 Justin Mayfield
Recipients Justin Mayfield, gvanrossum, thehesiod, vstinner, yselivanov
Date 2015-11-12.05:54:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I don't believe this is a case of nonidempotent callbacks, unless you are referring to Future.set_result(), which by design can't be called twice.  The callbacks are given an inconsistent opportunity to modify the poll set because of indeterminacy in the ioloop.  That being said I understand your reluctance given the amount of turmoil this has but would argue that consistency with tornado is a powerful ally and that a model where any callback using call_soon will be guaranteed the opportunity to modify the poll set is a good thing.
Date User Action Args
2015-11-12 05:54:24Justin Mayfieldsetrecipients: + Justin Mayfield, gvanrossum, vstinner, yselivanov, thehesiod
2015-11-12 05:54:24Justin Mayfieldsetmessageid: <>
2015-11-12 05:54:24Justin Mayfieldlinkissue25593 messages
2015-11-12 05:54:23Justin Mayfieldcreate