Use with logging module

In my module, I use the python logging module to print out messages.

During the operation which I want to monitor using alive-progress it may happen that messages are sent out using the logging module. Then, artifacts of the bar remain in the console:

Loading the fmu took 0.34800148010253906 s.

Starting simulation at t=0.0 s.          | ▁▃▅ 0/1000 [0%] in 0s (0.0/s, eta: ?)
Simulation took 0.7570006847381592 s.███▌| ▅▇▇ 990/1000 [99%] in 0s (1126.2/s, eta: 0s)
Simulation finished at t=1000.0 s.
|████████████████████████████████████████| 1000/1000 [100%] in 0.9s (1096.43/s)

The first message (“loading … took …”) was logged before i instantiated the alive bar. The other messages were emitted while the bar was active. I am using a vanilla StreamHandler that sends everything to stdout.

By the way - dunno if that’s possible - is it possible to have the alive bar redirected to a logging module, too? Might be interesting to have the complete (or not, in case of an error!) progress bar in a log file. Gives structure…

By the way 2: it’s pretty awesome 😃

Cheers, Jan

[rsalmei]

Hey, I’m glad to report I’ve finally mastered this! 🎉 The proper logging support will be included in the next major version!

on 0: WARNING:__main__:hey 0
on 80: WARNING:__main__:hey 80
|████████████████████████████████████████| 100/100 [100%] in 1.2s (85.97/s)

Now it is all automatically setup! The code to generate the above output is only:

from alive_progress import alive_bar
import time, logging

logging.basicConfig()
logger = logging.getLogger(__name__)

with alive_bar(100) as bar:
    for i in range(100):
        time.sleep(.01)
        if i % 80 == 0:
            logger.warning('hey %s', i)
        bar()

[TheTechRobo]

Wasn’t that the bug found with Windoze?