pytermgui VS AIOHTTP

Several libraries, such as urwid or PyTermGUI, allow the development of TUI applications in Python. For enhancing the functionality and aesthetics of TUI apps, they offer some fundamental and more sophisticated utilities. But there is one package that is truly exceptional and might even be so amazing that it sparks a TUI renaissance (I really wanted to put "TUI renaissance" somewhere in this article).

There are plenty of terminal UI libraries that are actually nice to work with. For Python, there's Textual and PyTermGUI. For Rust, there's ratatui and Cursive (or, if you want something a bit lower level, crosster or termion). For Go, there's bubbletea.

Talking about resources, their docs are pretty good and contains some examples too. Documentation: https://ptg.bczsalba.com/pytermgui.html

Have you tried PyTermGUI? It looks promising, but I wonder if there are any pitfalls. I need to build a professional CLI for a robot, and half-baked packages just won't do.

While the community is relatively small right now, my TUI framework PyTermGUI has a lot of the attributes you're looking for! We don't currently have a section dedicated to this yet, but if you come to the discord I'm sure we can help you :)

Check out the changelog here.

I suspect that the reason you didn't find much is that usually people need a whole textual user interface (or TUI). And there's quite a few libraries for those, like pytermgui or textual, and some more low-level tools in that area like prompt-toolkit

> AIOHTTP: The Python int constructor is used to parse Content-Lengths and chunk-sizes, so _, +, and - are misinterpreted.

Fun. I believe the fix is incomplete here[1]. Python's int() constructor accepts integers comprised of any unicode numeral, for example, int("٦٦٦") == 666, and "٦٦٦".isdecimal() == True.

[1] https://github.com/aio-libs/aiohttp/pull/7663/files#diff-197...

aiohttp

If you want speed, I would try to rewrite everything using an asynchronous library like aiohttp.

requests does not support async out-of-the-box, so we will use aiohttp to avoid complications. requests can do the job, and there is no substantial performance difference. But the code is more readable using aiohttp.

I'm using aiohttp to build an API server that sends TCP requests off to a seperate server. The module that sends the TCP requests is synchronous and a black box for my purposes. So my problem is that these requests are blocking the entire API. I need a way to wrap the module requests in an asynchronous coroutine that won't block the rest of the API.

aiohttp - Everything that I need and nothing that I don't.

Use aiohttp to download the content of each page of lists. As of this Code Review post, this is the only step we execute.

Reminds me of this post from 5 months ago, but it was for a Python library. I made a discussion thread on the aiohttp repo and someone ended up contacting the reddit admins about it. The problem seems to be resolved now.