To aid, I would propose we add logging to the package
- job name, args, kwargs + generating ID
- checking for lock
- creating lock
- clearing lock
By default, they'd be at a super-low logging level, e.g. DEBUG (or NOTSET?)
Additionally / optionally:
-
pure python example of setting the logging levels, to stdout, etc.
(this treads a bit into helping the user do what they could themselves as it's standard library, but I think that logging is actually configured/tweaked rarely enough its helpful to the user to see an example)
-
setting a global baseline, e.g. CELERY_SINGLETON_LOG_LEVEL, comparable to DJANGO_LOG_LEVEL
To aid, I would propose we add logging to the package
By default, they'd be at a super-low logging level, e.g.
DEBUG(orNOTSET?)Additionally / optionally:
pure python example of setting the
logginglevels, to stdout, etc.(this treads a bit into helping the user do what they could themselves as it's standard library, but I think that logging is actually configured/tweaked rarely enough its helpful to the user to see an example)
setting a global baseline, e.g.
CELERY_SINGLETON_LOG_LEVEL, comparable toDJANGO_LOG_LEVEL