Replies: 1 comment 2 replies
-
IMHO anything but very small applications shouldn't use |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This probably is more of a celery issue over flask however, I found lots of things online for django but none really for flask when it came to this issue.
The issue is when I'm using the logging module to log messages etc, it also makes a duplicate celery log at the same time.
I found this example on SO here
This will output 'log info from foo' in both the python logging module AND celery without bhd_logger.propagate = False
The solution was to set
bhd_logger.propagate = False
in this 5 year old thread. I was wondering if this was the recommended way? As this does seem to work as long as the python logger/celery logger does not sit on the same log level as celery. It seems to dead lock if I was to swap celery to the same logging level with this setup.Beta Was this translation helpful? Give feedback.
All reactions