Exceptions

exceptionasyncio.TimeoutError

The operation has exceeded the given deadline.

Important

This exception is different from the builtinTimeoutErrorexception.

exceptionasyncio.CancelledError

The operation has been cancelled.

This exception can be caught to perform custom operationswhen asyncio Tasks are cancelled. In almost all situations theexception must be re-raised.

Important

This exception is a subclass ofException, so it can beaccidentally suppressed by an overly broadtry..except block:

try:awaitoperationexceptException:# The cancellation is broken because the *except* block# suppresses the CancelledError exception.log.log('an error has occurred')

Instead, the following pattern should be used:

try:awaitoperationexceptasyncio.CancelledError:raiseexceptException:log.log('an error has occurred')
exceptionasyncio.InvalidStateError

Invalid internal state ofTask orFuture.

Can be raised in situations like setting a result value for aFuture object that already has a result value set.

exceptionasyncio.SendfileNotAvailableError

The “sendfile” syscall is not available for the givensocket or file type.

A subclass ofRuntimeError.

exceptionasyncio.IncompleteReadError

The requested read operation did not complete fully.

Raised by theasyncio stream APIs.

This exception is a subclass ofEOFError.

expected

The total number (int) of expected bytes.

partial

A string ofbytes read before the end of stream was reached.

exceptionasyncio.LimitOverrunError

Reached the buffer size limit while looking for a separator.

Raised by theasyncio stream APIs.

consumed

The total number of to be consumed bytes.