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 glangford
Recipients bquinlan, glangford, mark.dickinson, sbt, tim.peters, vstinner
Date 2014-01-30.22:26:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391120760.67.0.250291382963.issue20319@psf.upfronthosting.co.za>
In-reply-to
Content
An idea for a different possible fix - rather than cleaning up waiters in wait() and as_completed(), could they be removed in Future.set_result() and Futures.set_exception() ? 

I'm not certain if any waiter should ever be notified twice; if not, perhaps set_result() and set_exception() could just include

self._waiters = []

after all waiters have been signalled.
History
Date User Action Args
2014-01-30 22:26:00glangfordsetrecipients: + glangford, tim.peters, bquinlan, mark.dickinson, vstinner, sbt
2014-01-30 22:26:00glangfordsetmessageid: <1391120760.67.0.250291382963.issue20319@psf.upfronthosting.co.za>
2014-01-30 22:26:00glangfordlinkissue20319 messages
2014-01-30 22:26:00glangfordcreate