get_event_loop() Get the event loop for the current context. Returns an event loop object implementing the AbstractEventLoop interface. Raises an exception in case no event loop has been set for the current context and the current policy does not specify to create one. It must never return None.

set_event_loop(loop) Set the event loop for the current context to loop.

AbstractEventLoop.time() Return the current time, as a float value, according to the event loop’s internal clock.

AbstractEventLoop.stop() Stop running the event loop. This causes run_forever() to exit at the next suitable opportunity (see there for more details). Changed in version 3.5.1.

coroutine AbstractEventLoop.subprocess_shell(protocol_factory, cmd, *, stdin=subprocess.PIPE, stdout=subprocess.PIPE, stderr=subprocess.PIPE, **kwargs) Create a subprocess from cmd, which is a character string or a bytes string encoded to the filesystem encoding, using the platform’s “shell” syntax. This is similar to the standard library subprocess.Popen class called with shell=True. The protocol_factory must instanciate a subclass of the asyncio.SubprocessProtocol class. See subprocess_exe

coroutine AbstractEventLoop.subprocess_exec(protocol_factory, *args, stdin=subprocess.PIPE, stdout=subprocess.PIPE, stderr=subprocess.PIPE, **kwargs) Create a subprocess from one or more string arguments (character strings or bytes strings encoded to the filesystem encoding), where the first string specifies the program to execute, and the remaining strings specify the program’s arguments. (Thus, together the string arguments form the sys.argv value of the program, assuming it is a Python sc

coroutine AbstractEventLoop.sock_sendall(sock, data) Send data to the socket. Modeled after blocking socket.socket.sendall() method. The socket must be connected to a remote socket. This method continues to send data from data until either all data has been sent or an error occurs. None is returned on success. On error, an exception is raised, and there is no way to determine how much data, if any, was successfully processed by the receiving end of the connection. With SelectorEventLoop even

coroutine AbstractEventLoop.sock_accept(sock) Accept a connection. Modeled after blocking socket.socket.accept(). The socket must be bound to an address and listening for connections. The return value is a pair (conn, address) where conn is a new socket object usable to send and receive data on the connection, and address is the address bound to the socket on the other end of the connection. The socket sock must be non-blocking. This method is a coroutine. See also AbstractEventLoop.create_

coroutine AbstractEventLoop.sock_connect(sock, address) Connect to a remote socket at address. Modeled after blocking socket.socket.connect() method. With SelectorEventLoop event loop, the socket sock must be non-blocking. This method is a coroutine. Changed in version 3.5.2: address no longer needs to be resolved. sock_connect will try to check if the address is already resolved by calling socket.inet_pton(). If not, AbstractEventLoop.getaddrinfo() will be used to resolve the address. Se

coroutine AbstractEventLoop.sock_recv(sock, nbytes) Receive data from the socket. Modeled after blocking socket.socket.recv() method. The return value is a bytes object representing the data received. The maximum amount of data to be received at once is specified by nbytes. With SelectorEventLoop event loop, the socket sock must be non-blocking. This method is a coroutine.