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 bquinlan
Recipients Nam.Nguyen, bquinlan, r.david.murray
Date 2012-06-12.09:00:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339491614.89.0.115519452892.issue14119@psf.upfronthosting.co.za>
In-reply-to
Content
I've had people request that they be able control the order of processed work submissions. So a more general way to solve your problem might be to make the two executors take an optional Queue argument in their constructors.

You'd have to explain in detail in the document how the queues are used.

What do you think?
History
Date User Action Args
2012-06-12 09:00:15bquinlansetrecipients: + bquinlan, r.david.murray, Nam.Nguyen
2012-06-12 09:00:14bquinlansetmessageid: <1339491614.89.0.115519452892.issue14119@psf.upfronthosting.co.za>
2012-06-12 09:00:14bquinlanlinkissue14119 messages
2012-06-12 09:00:12bquinlancreate