➜

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, Nam.Nguyen, amaury.forgeotdarc, arekm, asvetlov, barry, doko, eric.araujo, georg.brandl, jcea, jeremybanks, lars.gustaebel, leonov, loewis, nadeem.vawda, nicdumz, nikratio, ockham-razor, pitrou, proyvind, rcoyner, shirish, strombrg, thedjatclubrock, tshepang, vstinner, ysj.ray
Date 2011-10-12.16:21:02
SpamBayes Score 3.3064282e-07
Marked as misclassified No
Message-id <1318436463.59.0.327982100213.issue6715@psf.upfronthosting.co.za>
In-reply-to
Content 
> To elaborate on the policy: giving bogus data in cases of race
> conditions is ok; crashing the interpreter or corrupting memory
> is not. If bogus data is given, it would be useful if the bogosity
> can be specified (e.g. when multiple threads read from the same
> POSIX file concurrently, they also get bogus data, but in a manner
> where each input byte is given to exactly one thread).

OK, that makes sense. My next patch will include per-compressor locks for
LZMACompressor and LZMADecompressor.

> To elaborate: ISTM that it's actually a bug in FileIO.

I've filed issue 13159 proposing that FileIO be fixed.
History
Date User Action Args
2011-10-12 16:21:03nadeem.vawdasetrecipients: + nadeem.vawda, loewis, barry, 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, strombrg, shirish, tshepang, jeremybanks, Nam.Nguyen
2011-10-12 16:21:03nadeem.vawdasetmessageid: <1318436463.59.0.327982100213.issue6715@psf.upfronthosting.co.za>
2011-10-12 16:21:03nadeem.vawdalinkissue6715 messages
2011-10-12 16:21:02nadeem.vawdacreate