musikcube VS typer

Nord theme for Musickube

Turns out someone already made an issue about this upstream, and even made a working ebuild, although it was published to his/her overlay which is not listed on overlays.gentoo.org yet sadly. If you're curious what was wrong and how it was fixed: the github issue

If it's just for music and you dig the look of TUI apps then musikcube has built-in server functionality. You install it on both the server and clients but keep the library on the server. It's light and works well, including for giant collections. There's apparently an android app too, musikdroid, but I haven't tried it. I haven't tried the windows or mac client apps either, so I can't vouch for any of them, but it's great on linux.

VLC can be used to play a file from the command line, but there is no user interface. Players like cmus and musikcube have a text based interface and library management.

Well, there's Musikcube. I think it's a solid choice over cmus.

music player: musikcube

Dont know about the rest but the top left music player looks like musikcube with a skin on it. https://musikcube.com/

I use https://github.com/clangen/musikcube on a daily basis

Musikcube, a cross-platform, terminal-based library, player and server\ (16 comments)

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/

interesting that you hate python, but love Click. Did you try Typer which uses Click underneath?