telnetlib3 without asyncio?

[alex4200]

Hello, would it be possible to create a telnetlib module without this asyncio overhead? In my case this makes the code EXTREMLY more cumbersome, unreadable and complicated. Thanks

[jquast]

Hello @alex4200, I understand the need to write code without asyncio and I would like to do that.

In the mean time, I suggest https://github.com/shmup/miniboa for a server without asyncio, @shmup maintains it well. As for client, even though python 3.11 warns that telnet.py is to be deprecated, you can simply copy telnet.py into your own project.

---

Roughly thinking, telnetlib3 without asyncio would still use asyncio under the hood.

[alex4200]

Thanks for your input @jquast

[Chef-de-IT]

I definitely support this enhancement, @jquast !

Transitioning from telnetlib to telnetlib3 would, for sure ,benefit from adding a sync API to the latter (with it being perfectly fine to use asyncio under the hood). Some use cases (e.g. AppDaemon in Home Assistant) make it fairly difficult to integrate and troubleshoot a telnetlib3 client without a sync way to interface with it, such as perhaps via a sync connection call and callbacks for any "see text from server and respond to it" shell interactions.