python/aqmp: Remove scary message
The scary message interferes with the iotests output. Coincidentally, if iotests works by removing this, then it's good evidence that we don't really need to scare people away from using it. Signed-off-by: John Snow <jsnow@redhat.com> Acked-by: Hanna Reitz <hreitz@redhat.com> Reviewed-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Hanna Reitz <hreitz@redhat.com> Message-id: 20211026175612.4127598-4-jsnow@redhat.com Signed-off-by: John Snow <jsnow@redhat.com>
This commit is contained in:
parent
49a608b8c2
commit
0f71c9a936
@ -22,7 +22,6 @@ managing QMP events.
|
||||
# the COPYING file in the top-level directory.
|
||||
|
||||
import logging
|
||||
import warnings
|
||||
|
||||
from .error import AQMPError
|
||||
from .events import EventListener
|
||||
@ -31,17 +30,6 @@ from .protocol import ConnectError, Runstate, StateError
|
||||
from .qmp_client import ExecInterruptedError, ExecuteError, QMPClient
|
||||
|
||||
|
||||
_WMSG = """
|
||||
|
||||
The Asynchronous QMP library is currently in development and its API
|
||||
should be considered highly fluid and subject to change. It should
|
||||
not be used by any other scripts checked into the QEMU tree.
|
||||
|
||||
Proceed with caution!
|
||||
"""
|
||||
|
||||
warnings.warn(_WMSG, FutureWarning)
|
||||
|
||||
# Suppress logging unless an application engages it.
|
||||
logging.getLogger('qemu.aqmp').addHandler(logging.NullHandler())
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user