tqdm VS typer

yeah my code needs to use multiprocessing, which does not play nice with tqdm. thanks for the tip about positions though, that helped me search more effectively and came up with two promising comments. unmerged / require some workarounds, but might just work:

https://github.com/tqdm/tqdm/issues/1000#issuecomment-184208...

> Like tqdm (Python progressbar library) but as a Unix utility.

FYI: tqdm can be used in a shell pipeline as well. It's documented (at least) in their readme: https://github.com/tqdm/tqdm#module

BTW, my inspiration was https://github.com/tqdm/tqdm library for python and any contribution is welcome to add similar functionality.

I can recommend you the package tqdm (https://github.com/tqdm/tqdm) You can replace the standard for statement with it, or use it with any other iterable. By default, it gives you a progress bar with a percentage and ETA, but you can also configure it to only print the percentage, if you want that. If you want to use print statements, adding \r at the beginning and not putting a line end should also do the trick.

you try to run an python script that requires the tqdm package and also a regex package (what normally should be installed, when installing python). Blender tries to install these packages without success. You probably have to do it on your own by installing them in your pythons virtual environment.

If OP is using python that might be the output of python's tqdm.

I have a client-server socket program where the server sends a file to the client. The server is designed to allow multiple clients using threading. For the file transfer on the client, I am using the tqdm library (https://github.com/tqdm/tqdm).

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?