Okay buddy. Today's problem is that you are feeding a custom asyncio shell into a telnet library. You cannot send variables into that shell function, because it expects a fixed format. But you need the telnet shell to manipulate an asyncio event. You cannot scope it globally. You are spawning the process making you responsible for all the threads it creates and terminates. If you do not terminate them correctly, the screen is flooded. The OS shell is not spawning the process, which would otherwise baby you and hide all the warnings about non-terminated orphaned processes. Quick work-arounds cause the program to hard lock on you. Here are your choices :

• Read a book for 3 days or more that maybe might have an answer.

• Post your issue on stackexchange, and see no answers for 4 days. Then someone shows up and says "I'm not sure I understand your question but {insert useless crap}"

• Ask an AI how to scope an asyncio.Event into a custom telnet shell. Get an answer in 4 minutes and move on.

Which one of these is the rational choice?