The reason why asyncio cannot handle ctrl-c gracefully by default is?

that the asyncio event loop is not designed to handle signals by?

default. When a signal is received, the event loop will raise a?

KeyboardInterrupt exception, which can cause tasks to be cancelled?

abruptly, leading to data loss or other unexpected behavior.

On the other hand, C++ Boost.Asio can handle ctrl-c gracefully by?

default because it has built-in support for signal handling. Boost.Asio?

provides an interface for registering signal handlers and allows signals?

to be handled asynchronously, so that tasks can be cleanly cancelled?

without losing data or encountering unexpected behavior.