refactor socket shadowing

[reactive-firewall]

This probably isn't the only instance, so

⚠️ Potential issue

Avoid shadowing the socket module

In the handle method of MyUDPHandler, the variable socket is assigned as self.request[1], which shadows the socket module imported earlier. This can lead to confusion and potential bugs if the socket module is used later in the code.

Consider renaming the variable to avoid shadowing. For example:

-def handle(self):
-	data = self.request[0].strip()
-	socket = self.request[1]
+def handle(self):
+	data = self.request[0].strip()
+	conn = self.request[1]
	print(str("{} wrote:").format(self.client_address[0]))
	print(data)
-	socket.sendto(data.upper(), self.client_address)
+	conn.sendto(data.upper(), self.client_address)

Committable suggestion was skipped due to low confidence.

• Identify shadowing instances
• refactor those instances

[coderabbitai]

Here are five alternative variable names for the UDP socket variable, following the project's naming style:

1. udp_socket
2. udp_sock
3. udp_socket_obj
4. udp_sock_fd
5. udp_sock_handle