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 dan.oreilly
Recipients andreasvc, bquinlan, dan.oreilly, giampaolo.rodola, josh.r, mark.dickinson, mdengler, pitrou
Date 2014-08-10.18:57:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1407697049.65.0.617520859935.issue21423@psf.upfronthosting.co.za>
In-reply-to
Content
Here's an updated patch. Changes:

* Fixed what appears to have been a find/replace typo I made prior to uploading the previous patch.

* The tracebacks from the negative unit tests are now suppressed. 

* Fixed a race condition in the initializer failure handling for ThreadPoolExecutor. Futures that were submitted before the initializer actually failed will now raise a RuntimeError indicating that initializer failed.

* Suppressed an occasional queue.Full exception that would pop up while shutting down a ProcessPoolExecutor that was broken due to an initializer fail. As best as I can tell the exception is harmless, so suppressing it should be ok.

*Updated the docs.
History
Date User Action Args
2014-08-10 18:57:30dan.oreillysetrecipients: + dan.oreilly, bquinlan, mark.dickinson, pitrou, giampaolo.rodola, mdengler, josh.r, andreasvc
2014-08-10 18:57:29dan.oreillysetmessageid: <1407697049.65.0.617520859935.issue21423@psf.upfronthosting.co.za>
2014-08-10 18:57:29dan.oreillylinkissue21423 messages
2014-08-10 18:57:29dan.oreillycreate