Christian wrote: > > Make file objects as thread safe as the underlying libc FILE* > > implementation. > > close() will now raise an IOError if any operations on the file object > > are currently in progress in other threads. > > > > Most code was written by Antoine Pitrou (pitrou). Additional testing, > > documentation and test suite cleanup done by me (gregory.p.smith). > > > > Fixes issue 815646 and 595601 (as well as many other bugs and > > references to this problem dating back to the dawn of Python). > > How much of the code needs to go into Python 3000? Python 3000 exposes > only file descriptors and not wrapepd FILE*. It should be safe without > the patch, shouldn't it?
If you are curious you could port the unit tests to py3k and see in which kinds of ways they fail :) Then we can debate whether, and how, we should make FileIO objects thread-safe. cheers 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
