| commit | 3c1e16c60c72e8f11a15d63e9d4a2fd33be6b106 | |
| author | Cleber Rosa <crosa@redhat.com> | |
| Thu, 11 Feb 2021 22:01:41 +0000 (11 17:01 -0500) | ||
| committer | Cleber Rosa <crosa@redhat.com> | |
| Tue, 16 Feb 2021 02:40:16 +0000 (15 21:40 -0500) | ||
| tree | dc2701498a498769bebb9bd3a92d545c0709c96a | treesnapshot (tar.gz zip) |
| parent | 3e5c180be0ccf6ced16b76ed552182f364e5da6c | commitdiff |
Python: close the log file kept by QEMUMachine before reading it
Closing a file that is open for writing, and then reading from it
sounds like a better idea than the opposite, given that the content
will be flushed.
Reference: https://docs.python.org/3/library/io.html#io.IOBase.close
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20210211220146.2525771-2-crosa@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Closing a file that is open for writing, and then reading from it
sounds like a better idea than the opposite, given that the content
will be flushed.
Reference: https://docs.python.org/3/library/io.html#io.IOBase.close
Signed-off-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20210211220146.2525771-2-crosa@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Signed-off-by: Cleber Rosa <crosa@redhat.com>
| python/qemu/machine.py | diffblobblamehistory |