Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment: Debugging threading problems is never as simple as it seems. I don't believe logging is breaking because of some interaction with the system calls - rather, the presence of the system calls is changing the real-time characteristics of the system and exposing the failure.
This problem is not directly related to logging - for example, see http://groups.google.com/group/comp.lang.python/browse_thread/thread/98fa9592e7c47130/d5642964c573dfc0#d5642964c573dfc0 I will look to see if I can find what the exact problem is. Did you turn off Windows search indexing for the volume before running the test, in addition to turning off the anti-virus? It looks as if something else is opening the file (which, in our test, will have been very recently written to when the error occurs) and the suspicion must fall on anti-virus or search indexing or some other file watching software (e.g. backup software which is configured to monitor all file changes and refresh the backup copy in pseudo-real-time). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4749> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
