Gregory P. Smith <greg <at> krypto.org> writes: > > http://bugs.python.org/issue3618 is a release blocker due to deadlock > in the io library. > > and the related C RLock implementation in [etc.]
By the way, please note using an RLock will just solve the deadlock bug. It won't make the behaviour of write() and friends absolutely correct if called recursively, rather than lose or duplicate chunks of bytes. Those functions are not meant to be reentrant at all. Which means, perhaps another way of solving the bug would be to ensure tracing is disabled when entering those functions. Are there cases of reentrancy apart from tracing? signals and other asynchronous stuff perhaps? Regards Antoine. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
