Nadeem Vawda <nadeem.va...@gmail.com> added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6715> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
