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 giampaolo.rodola, pitrou, serhiy.storchaka
Date 2012-12-28.15:05:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1356707155.62.0.231948626379.issue16640@psf.upfronthosting.co.za>
In-reply-to
Content
What is the point of having heapq.heappush under a lock if heapq.heappop in another method is not protected? The logic doesn't seem to make sense.
History
Date User Action Args
2012-12-28 15:05:55pitrousetrecipients: + pitrou, giampaolo.rodola, serhiy.storchaka
2012-12-28 15:05:55pitrousetmessageid: <1356707155.62.0.231948626379.issue16640@psf.upfronthosting.co.za>
2012-12-28 15:05:55pitroulinkissue16640 messages
2012-12-28 15:05:55pitroucreate