New submission from Thomas Moreau <thomas.moreau.2...@gmail.com>: If the methods `set` and `clear` of `multiprocessing.Event` are called one after another, while a `multiprocessing.Process` calls `wait`, the `Event` does not match the documented behavior (https://docs.python.org/3.7/library/threading.html#threading.Event.wait) and the call to wait can return `False` even though the call to wait did not timeout (This happens both with `timeout=30` or `timeout=None`).
Attached is a script reproducing this issue. The documentation should either be changed or the behavior should be updated. ---------- components: Library (Lib) files: concurrent_event.py messages: 305960 nosy: tomMoral priority: normal severity: normal status: open title: Race condition in wait with timeout for multiprocessing.Event type: behavior versions: Python 3.6 Added file: https://bugs.python.org/file47256/concurrent_event.py _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31991> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
