yad VS typer

Aside from the obvious uses - command line scripts - you can also do quite a bit with the GUI. Check out Yad for bash script GUI. X11 related tools like wmctrl, xdotool allow you to create spectacular scripts. I write and use numerous dynamic menus created with bash + jgmenu.

Are you referring to yad?

git clone https://github.com/v1cont/yad.git yad-dialog-code

yad - Program allows you to display GTK+ dialog boxes from command line or shell scripts. YAD depends on GTK+ only.

yad pushing your shell scripts to the next level via user inputs. For example i wrote a small script which lets me select an environment and an app and the url+port is written into the clipboard.

I make a lot of use of yad (which I think is in the standard repository) to give a GUI-like feel to my scripts. yad is a significant advance over zenity.

make a binding on an empty workspace that calls a yad script at the cursor

You might want to look at yad to add a GUI dialogue box to your script. Something like:

I like yad[0] for this. For example, I use it to present a GUI color picker to change/insert colors in Vim (via a plugin called vCoolor[1]). I also use it in some i3/sway scripts that need user input or to show a progress bar.

[0]: https://github.com/v1cont/yad

[1]: https://github.com/KabbAmine/vCoolor.vim

zenity should be a simple start https://gitlab.gnome.org/GNOME/zenity (and apparently there is a fork too https://github.com/v1cont/yad but haven't tried it)

He is probably most well know for creating FastAPI that I taught to some of my clients and Typer that I've never used.

I have been using Typer on every one of my CLI projects which uses Click under the hood. The documentation is fantastic, the CLI app it produces looks great and lets you create things quickly. I high recommend it.

https://typer.tiangolo.com/

Adding CLI capabilities. My preferred library here is typer.

I just heard about this but it seems to be pretty much the type of thing you want and want fast.

Docstrings are for documenting how a function/ class/ method/ module works. Often you don't need to add a docstring to your main function because no one will be importing it to use elsewhere. And if you want it to run as a CLI, then there are better ways to document the available options. For example, typer does most of it for you, or in click you add the help text to the decorator.

Most computing tasks in airflow DAGs are KubernetesPodOperator containing a CLI (Python Typer). It allows us to pass arguments easily to run DAG manually if needed (the new UI to pass arguments to DAG in airflow 2.6 is really nice). Arguments allow us to replay DAG easily (change start / end dates for instance).

So it's basically the main .gitlab-ci.yml file plus a separate Python CI app using Typer for the AWS instrumentation.

Similarly for Typer, which is literally "the FastAPI of CLIs"[1]. Handy to type your `main` parameters and have CLI argument parsing. For more complicated cases, it's a wrapper around Click.

[1] https://typer.tiangolo.com/