Fabre Lambeau

I ended up replacing this with ``` with progressbar.ProgressBar( prefix='\x1b[33mDownloading files - \x1b[39m | Downloaded {variables.dld} | Skipped {variables.skpd} ', variables={'dld': '--', 'skpd': '--'}, max_value=progressbar.UnknownLength) as bar: for response in...

Your explanation makes sense, and I had actually thought of doing something like that. It doesn't seem "clean" though: 1 process in charge of 2 radically different things - goes...

I've also tried: ``` format_custom_text = progressbar.FormatCustomText( 'Spam: %(spam).1f kg, eggs: %(eggs)d', dict( spam=0.25, eggs=3, ), ) bar = progressbar.ProgressBar(widgets=[format_custom_text]) bar.start() for i in range(25): format_custom_text.update_mapping(eggs=i * 2) time.sleep(0.1) bar.update(i)...

@pandhora That only works if you don't have another part of the dash that's already using selected_rows as output however...

I stand corrected! Many thanks for that @terminalstderr

Yes, I'm aware of the multi-bar (I already use it for something else), but here the 2 processes are (almost) completely independent and of different nature, so the multi-bar wouldn't...

I will test this and get back to you.

You did not add an example in the examples.py file from what I can see. Would be nice to have one!

@prkumar i could really do with this too… for the same reason: logging. In particular logging of requests that may fail (and therefore i can’t use response.request in the response_handler

Has there ever been any attempt to implement this into the package?