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 nadeem.vawda
Recipients cantor, nadeem.vawda, pitrou
Date 2013-10-25.21:12:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382735554.71.0.231131972898.issue19395@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, that's because the builtin map function doesn't handle each input
in a separate process, so it uses the same LZMACompressor object
everywhere. Whereas multiprocessing.Pool.map creates a new copy of the
compressor object for each input, which is where the problem comes in.
History
Date User Action Args
2013-10-25 21:12:34nadeem.vawdasetrecipients: + nadeem.vawda, pitrou, cantor
2013-10-25 21:12:34nadeem.vawdasetmessageid: <1382735554.71.0.231131972898.issue19395@psf.upfronthosting.co.za>
2013-10-25 21:12:34nadeem.vawdalinkissue19395 messages
2013-10-25 21:12:34nadeem.vawdacreate