➜

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 pitrou
Recipients Albert.Strasheim, aljungberg, asksol, bquinlan, brian.curtin, gdb, gkcn, hongqn, jcea, jnoller, neologix, pitrou, python-dev, vlasovskikh, vstinner
Date 2011-06-08.15:25:30
SpamBayes Score 0.0016505879
Marked as misclassified No
Message-id <1307546730.69.0.457894542929.issue9205@psf.upfronthosting.co.za>
In-reply-to
Content 
So, concurrent.futures is fixed now. Unless someone wants to patch multiprocessing.Pool, I am closing this issue.
History
Date User Action Args
2011-06-08 15:25:30pitrousetrecipients: + pitrou, jcea, bquinlan, vstinner, jnoller, hongqn, brian.curtin, asksol, vlasovskikh, neologix, gdb, Albert.Strasheim, aljungberg, python-dev, gkcn
2011-06-08 15:25:30pitrousetmessageid: <1307546730.69.0.457894542929.issue9205@psf.upfronthosting.co.za>
2011-06-08 15:25:30pitroulinkissue9205 messages
2011-06-08 15:25:30pitroucreate