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 asksol
Recipients asksol, bquinlan, jnoller
Date 2010-10-24.08:29:47
SpamBayes Score 0.010955874
Marked as misclassified No
Message-id <1287908989.37.0.125196922629.issue7200@psf.upfronthosting.co.za>
In-reply-to
Content
Queue uses multiprocessing.util.Finalize, which uses weakrefs to track when the object is out of scope, so this is actually expected behavior.

IMHO it is not a very good approach, but changing the API to use explicit close methods is a little late at this point, I guess.
History
Date User Action Args
2010-10-24 08:29:49asksolsetrecipients: + asksol, bquinlan, jnoller
2010-10-24 08:29:49asksolsetmessageid: <1287908989.37.0.125196922629.issue7200@psf.upfronthosting.co.za>
2010-10-24 08:29:48asksollinkissue7200 messages
2010-10-24 08:29:47asksolcreate