A class will let you bundle together the behavior and state of an object. Observe the following diagram for better understanding: The following points are worth breath-first or depth-first. By default, Python goes with the depth-first. That’s is why in the below diagram the Python searches the dothis() method first in class A. So the method resolution order in the the below example will be Mro- D->B->A->C Look at the below multiple inheritance diagram: OOP in Python 52

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 172 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 174 Chapter 6. Developer guide conda Documentation

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 168 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 170 Chapter 6. Developer guide conda Documentation

which is always called exactly once when the TCP connection is closed. Coroutines The following diagram shows which coroutines are running at each stage of the connection lifecycle on the client side. defined on the WebSocketServerProtocol and WebSocketClientProtocol classes. Data flow The following diagram shows how data flows between an application built on top of websockets and a remote endpoint. It connection termination is discussed in another section below. Receiving data The left side of the diagram shows how websockets receives data. Incoming data is written to a StreamReader in order to implement

which is always called exactly once when the TCP connection is closed. Coroutines The following diagram shows which coroutines are running at each stage of the connection lifecycle on the client side. defined on the WebSocketServerProtocol and WebSocketClientProtocol classes. Data flow The following diagram shows how data flows between an application built on top of websockets and a remote endpoint. It connection termination is discussed in another section below. Receiving data The left side of the diagram shows how websockets receives data. Incoming data is written to a StreamReader in order to implement

which is always called exactly once when the TCP connection is closed. Coroutines The following diagram shows which coroutines are running at each stage of the connection lifecycle on the client side. defined on the WebSocketServerProtocol and WebSocketClientProtocol classes. Data flow The following diagram shows how data flows between an application built on top of websockets and a remote endpoint. It connection termination is discussed in another section below. Receiving data The left side of the diagram shows how websockets receives data. Incoming data is written to a StreamReader in order to implement

TCP connection is closed. 49 websockets Documentation, Release 9.0 Coroutines The following diagram shows which coroutines are running at each stage of the connection lifecycle on the client side. defined on the WebSocketServerProtocol and WebSocketClientProtocol classes. Data flow The following diagram shows how data flows between an application built on top of websockets and a remote endpoint. It below. 4.1. Design 51 websockets Documentation, Release 9.0 Receiving data The left side of the diagram shows how websockets receives data. Incoming data is written to a StreamReader in order to implement

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 4 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 4.6. Developer guide 309 conda, Release 23.10.1

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 170 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 172 Chapter 5. Developer guide conda, Release 23

the diagram interacts with other systems and how users relate to it. More information about how to interpret this diagram can be found in the C4 model documentation about the System Context diagram. 4 Container This level is zooming in to conda on a system level, which was in the center of the Level 1 diagram, to show the high- level shape of the software architecture of and the various responsibilities in in the C4 model documentation about the Container diagram. Channels The following diagram focuses on the channels container from the level 1 diagram. 4.6. Developer guide 311 conda, Release 23.11.1