py_cui VS rich

py_cui - Another curses wrapper

It's great to see some more competitors on the TUI front of the Python ecosystem! I recently tried multiple existing frameworks and was not particularly happy with the state.

Here are the main contenders for libraries that provide higher-level API than urwid/ncurses:

* Picotui, https://github.com/pfalcon/picotui

* Npyscreen, https://github.com/npcole/npyscreen

* py_cui, https://github.com/jwlodek/py_cui

Both Picotui and Npyscreen are relatively unmaintained / considered feature-full. py_cui seems to be in the best shape.

Fingers crossed for this project making it through, building on top of Rich gives it quite a bit of headstart. You can also sponsor @willmcgugan on Github [0].

[0]: https://github.com/sponsors/willmcgugan

You're probably going to want to do this in a TUI. If I was going to attempt this project, I think I'd try py_cui which was written by a fellow Redditor u/QbaPolak17. Another possible (buy maybe less pretty) option is picotui. I've not implemented either of these, but py_cui looks fun.

So, when I found the different commands to get back my file and recover it, I wanted to create a clear UI to do it. Searching for a CUI library, I've stumbled upon py_cui, based on curses, it has a really easy learning curve. Easy to get it running.

I dit it with py_cui, it's based on curses library but really easier to work with.

There is an open issue [1] on GitHub to make it more modular and get rid of markdown and syntax highlighting but I have no hope for rich to get more minimal.

[1]: https://github.com/Textualize/rich/issues/2277

I hope he doesn't mind, but the creator of Rich and Textualize is a good guy, and Scottish: https://www.willmcgugan.com/about/

https://www.textualize.io/

https://github.com/Textualize/rich

They keep getting improved error messaging and this is one of my favorite features. But I'd love if we could get some real rich text. Idk if anyone else uses rich, but it has infected all my programs now. Not just to print with colors, but because it makes debugging so much easier. Not just print(f"{var=}") but the handler[0,1]. Color is so important to these types of things and so is formatting. Plus, the progress bars are nice and have almost completely replaced tqdm for me[2]. They're just easier and prettier.

[0] https://rich.readthedocs.io/en/stable/logging.html

[1] Try this example: https://github.com/Textualize/rich/blob/master/examples/exce...

[2] Side note: does anyone know how to get these properly working when using DDP with pytorch? I get flickering when using this and I think it is actually down to a pytorch issue and how they're handling their loggers and flushing the screen. I know pytorch doesn't want to depend on rich, but hey, pip uses rich so why shouldn't everyone?

colors.crumb extends Crumb with basic terminal styling functions and RGB, HEX, ANSI conversion functions. It is in the realm of JavaScript's chalk and Python's rich but slightly more functional 😉.

I am working on a new python project and one of the first things I added was https://github.com/Textualize/rich because of how easy it is to make things look good in the terminal.

I am not rewriting anything but I'd love to have a library like `rich` in Rust: https://github.com/textualize/rich

Add some cool-looking stuff to your output with rich.

You might consider taking inspiration from the rich module. In particular, I like how rich supports inline color theming which seems much more cumbersome in your framework, requiring the use of context managers as well as familiarity with how your framework structures color objects. Other than that though, I'm impressed!

Today I released coBib 4.0, my console bibliography manager written in Python, which now uses rich and textual to provide a cohesive and modern user experience in both its CLI and TUI.