Right, this doesn't apply to py3k files at all. (Not that py3k files are all that thead-safe. :-)
On Mon, Apr 7, 2008 at 8:42 AM, Christian Heimes <[EMAIL PROTECTED]> wrote: > gregory.p.smith schrieb: > > > Author: gregory.p.smith > > Date: Mon Apr 7 01:11:17 2008 > > New Revision: 62195 > > > > Modified: > > python/trunk/Doc/c-api/file.rst > > python/trunk/Include/fileobject.h > > python/trunk/Lib/test/test_file.py > > python/trunk/Misc/NEWS > > python/trunk/Objects/fileobject.c > > Log: > > 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? > > Christian > _______________________________________________ > Python-3000 mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-3000 > Unsubscribe: > http://mail.python.org/mailman/options/python-3000/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
