Vinay Sajip added the comment:
There *is* a race condition with WatchedFileHandler - see #14632 - but there is
not much that can be done about it (see the various comments in that issue).
BTW, I wasn't able to reproduce the threading problem from your script: there
were no errors and the file
Roundup Robot added the comment:
New changeset bb8b0c7fefd0 by Vinay Sajip in branch '2.7':
Issue #21742: Set stream to None after closing.
http://hg.python.org/cpython/rev/bb8b0c7fefd0
New changeset 6f1f38775991 by Vinay Sajip in branch '3.4':
Issue #21742: Set stream to None after closing.
New submission from Vishvananda Ishaya:
If there is a failure during the re-opening of the file WatchedFileHandler can
lose the ability to log and starts throwing IOErrors.
--
messages: 220403
nosy: vishvananda
priority: normal
severity: normal
status: open
title: WatchedFileHandler
Vishvananda Ishaya added the comment:
The attached file illustrates the error when attempting to call handler.emit()
from multiple threads at the same time.
--
Added file: http://bugs.python.org/file35604/log.py
___
Python tracker
Vishvananda Ishaya added the comment:
The attached file illustrates the error when attempting to call handler.emit()
when the file cannot be opened. Even if this situation is later remedied all
future emit() calls will fail since stream.flush() is called on a fd that has
already been closed.
Vishvananda Ishaya added the comment:
Example diff against python 2.7.6 that fixes the issues
--
keywords: +patch
Added file: http://bugs.python.org/file35606/log.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21742
Changes by Ned Deily n...@acm.org:
--
nosy: +vinay.sajip
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21742
___
___
Python-bugs-list mailing list
