Logging Issues about flask-apscheduler HOT 3 CLOSED

First of all, it only happens with Python 2.7, in Python 3.4 it works fine because the logging library has different behaviour between those versions.

Flask uses a logger called werkzeug with one handler StreamHandler attached into it that writes everything into the console. If you want you can check this out here: https://github.com/mitsuhiko/werkzeug/blob/master/werkzeug/_internal.py#L80

APScheduler uses another logger called apscheduler.executors, by default this logger doesn't have any handler attached for this reason you see this message No handlers could be found for logger.

Why does it work when calling basicConfig()?
Because this method attach a new StreamHandler to the logger called root, any unhandled log is handled by this root logger, it is a behaviour from logging library.

If you add manually a StreamHandler to the Root Logger it will works too.

logger = logging.getLogger()  # this returns the root logger 
logger.addHandler(logging.StreamHandler())

Usually I fix it just calling basicConfig() in the app startup

Any question let me know.

Cheers!

from flask-apscheduler.

Thanks, I switched to Python 3 and fixed the problem. I haven't got it working with python 2.7. I'll look into it when I have the time and post the code. Thanks again.

from flask-apscheduler.

Ok, I will close it for now.
Cheers!

from flask-apscheduler.