On 10/9/20 7:51 PM, John Snow wrote:
We enabled callers to interface directly with settimeout, but this
reacts poorly with blocking/nonblocking operation; as they are using the
same internal mechanism.
1. Whenever we change the blocking mechanism temporarily, always set it
back to what it was afterwards.
2. Disallow callers from setting a timeout of "0", which means
Non-blocking mode. This is going to create more weird problems than
anybody wants, so just forbid it.
I opt not to coerce '0' to 'None' to maintain the principal of least
surprise in mirroring the semantics of Python's interface.
Signed-off-by: John Snow <js...@redhat.com>
---
python/qemu/qmp.py | 23 +++++++++++++++++------
1 file changed, 17 insertions(+), 6 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <phi...@redhat.com>
