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, vstinner
Date 2014-01-23.18:26:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390501574.92.0.253419196403.issue20297@psf.upfronthosting.co.za>
In-reply-to
Content
> - you replaced the _AcquireFutures context manager on all futures with an >individual lock. In my opinion, it should be changed in a different patch. I >don't know which option is better, but if it is changed, it should be changed >in the whole file.

I can pursue the replacement of _AcquireFutures in a different patch, however I don't necessarily agree that it should be changed in the whole file. as_completed() is different than wait(), since wait() is obligated to return done and notdone Futures, which might require a different implementation. Initially, it may be better to only change as_completed(), where there is a clear concurrency win.
History
Date User Action Args
2014-01-23 18:26:14glangfordsetrecipients: + glangford, bquinlan, mark.dickinson, vstinner
2014-01-23 18:26:14glangfordsetmessageid: <1390501574.92.0.253419196403.issue20297@psf.upfronthosting.co.za>
2014-01-23 18:26:14glangfordlinkissue20297 messages
2014-01-23 18:26:14glangfordcreate