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 neologix
Recipients gkcn, jnoller, neologix, petri.lehtinen, terry.reedy
Date 2011-05-28.22:10:28
SpamBayes Score 0.024792574
Marked as misclassified No
Message-id <1306620629.07.0.0620410051897.issue12157@psf.upfronthosting.co.za>
In-reply-to
Content
When map is called, a MapResult object is created, which adds itself to the Pool's result cache.
When the pool is shut down, the result handler thread waits until the cache drains (while cache and thread._state != TERMINATE). But since no result is posted to the result queue (since the iterable is empty), the result handler never receives any task, and never gets to drain the cache. It thus waits forever on the recv on the result queue.
History
Date User Action Args
2011-05-28 22:10:29neologixsetrecipients: + neologix, terry.reedy, jnoller, gkcn, petri.lehtinen
2011-05-28 22:10:29neologixsetmessageid: <1306620629.07.0.0620410051897.issue12157@psf.upfronthosting.co.za>
2011-05-28 22:10:28neologixlinkissue12157 messages
2011-05-28 22:10:28neologixcreate