asciimatics VS click

For small apps, I may choose a TUI (Terminal User Interface). Curses for Python is very lightweight, but quite low level and difficult to use for anything more than a very simple interface (if your app tries to draw outside of the drawing area, the app crashes, so you have to carefully manage every detail). Textual and asciimatics are both mature TUI frameworks that provide a higher level and more Pythonic way to create TUI's.

If you are looking for something more flexible that just printing to a terminal, take a look at Asciimatics and textual. Both are available from Pypi.

Scroll down to the TUI example in the README, just above the documentation link: https://github.com/peterbrittain/asciimatics

Download fireworks.py

Source code: https://github.com/peterbrittain/asciimatics/blob/master/samples/fireworks.py

I have made yet another ssh connection manager with TUI, using asciimatics and tinyDB.

Personally I dig the aesthetics of asciimatics, it's quite handy and cross-platform.

I've used asciimatics in the past to good effect.

Take a look at rich (kinda new, but pretty neat), asciimatics, or urwid

Context: "click" - "Command Line Interface Creation Kit" - easily create CLIs from Python code, via adding decorators: https://github.com/pallets/click

"click-web" in turn turns the click CLI app into a web app with one line of code.

there is also click, it is more straight forward and also nice to keep the relevant code where the code is. https://github.com/pallets/click/

I don't have huge experience with Python, but I used async code with C#/Typescript and lately I had to use some asyncio magic.

I found this article: https://blog.dalibo.com/2022/09/12/monitoring-python-subproc... and while async/await syntax is the same, it's not entirely clear for me, why there's some event loop and what exactly happens, when I pass function to asyncio.run(), like here: https://github.com/pallets/click/issues/85#issuecomment-5034...

So, you can use it and it's not that hard, but there are some parts that are vague for me, no matter which language implements async support.

Hmm… did you try such approaches, as [click](https://github.com/pallets/click) or[tap](https://github.com/swansonk14/typed-argument-parser)?

This app leverages these powerful libraries: - yt-dlp: video downloader - moviepy: video trimmer/merger - click: CLI app creator - rich / rich-click: CLI app styler

I've used click [1] a lot to build Python tooling scripts the past few years. Click usage is "sort of" similar to the author's proposed solution. There's also a small section here [2] that describes some of the issues covered in the article (in context of argparse).

[1] - https://github.com/pallets/click

I think the success of Arduino in the hardware world can be explained in a similar way, as the relative success of "command line app frameworks" like Click[1], or even much lighter-weight libraries like argparse[2]. You absolutely can get away with using just getopt[3] (and people experienced with it will likely strongly prefer it). However certain factors such as a more declarative API, a nice logo, the existence of an ecosystem (even if you're not actively drawing from it), an official "branded" forum, etc can all play into picking a more complex solution, with more baggage you don't need, certain oddities that may throw users off, etc.

[1]: https://click.palletsprojects.com/

[2]: https://docs.python.org/3/library/argparse.html

[3]: https://man.openbsd.org/getopt.3, https://linux.die.net/man/3/getopt

Exactly! You can also use a library like click (https://github.com/pallets/click) to help take care of the command line side, while you focus on the 'business logic' of your application :)