Terry Reedy wrote:
I believe the C standard specifies that the behavior of mixed reads and writes is undefined without intervening seek and/or flush, even if the seek is ignored (as it is on some Unix systems). With two threads, the timing is undetermined.
It's also possible that the stdio object is being locked while one of the threads is using it, which would also account for the observed half-duplex behaviour. Another good reason to steer clear of file objects! -- Greg -- http://mail.python.org/mailman/listinfo/python-list
