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 Christophe Simonis, Garen, amaury.forgeotdarc, arekm, asvetlov, doko, eric.araujo, georg.brandl, jcea, jreese, lars.gustaebel, leonov, loewis, nadeem.vawda, nicdumz, nikratio, ockham-razor, pitrou, proyvind, rcoyner, shirish, strombrg, thedjatclubrock, vstinner, ysj.ray
Date 2011-04-08.00:20:00
SpamBayes Score 0.0004798
Marked as misclassified No
Message-id <1302222004.24.0.429181688506.issue6715@psf.upfronthosting.co.za>
In-reply-to
Content
> As a reference, I think you are refering to #5863 and #10791. Pretty fine job, I must say.

Thank you :)

> Nadeem, what do you think?. Is xz in your list?.

Yes, it's the next substantial thing I was planning on working on. I don't have
a lot of free time at the moment, though, so it might take a while. But I'll
definitely have it done in time for the release of 3.3 ;)

Looking at the pyliblzma code, I see that it provides the same thread-safety
guarantees as bz2 does. In rewriting, I would like to remove the locking code,
as it complicates the control flow logic of the C code, and doesn't seem like
the sort of thing a compression library should be concerned with. Are there any
objections to this? (Also, if anyone knows why bz2 was written to be thread-safe
in the first place, please enlighten me)
History
Date User Action Args
2011-04-08 00:20:04nadeem.vawdasetrecipients: + nadeem.vawda, loewis, georg.brandl, doko, jcea, amaury.forgeotdarc, arekm, lars.gustaebel, pitrou, vstinner, nicdumz, eric.araujo, Christophe Simonis, rcoyner, proyvind, asvetlov, nikratio, leonov, Garen, ysj.ray, thedjatclubrock, ockham-razor, jreese, strombrg, shirish
2011-04-08 00:20:04nadeem.vawdasetmessageid: <1302222004.24.0.429181688506.issue6715@psf.upfronthosting.co.za>
2011-04-08 00:20:02nadeem.vawdalinkissue6715 messages
2011-04-08 00:20:00nadeem.vawdacreate