I wrote an extension of the celery.schedules.schedule
interface, and I can't figure out why it's getting instantiated with nothing set in the extra values I created.
When I instantiate them before passing to app.conf.CELERYBEAT_SCHEDULE
they're correct. But all the ones that celery beat instantiates are incorrect.
I asked in #celery IRC chan and the only response I got was about lazy mode, but that's for celery.beat.Scheduler
, not celery.schedules.schedule
, so if it's relevant, I don't understand how. Do I have to extend that too, just so that it instantiates the schedules correctly?
I've tried digging into the celery code w/the debugger to figure out where these schedules are getting instantiated and I can't find it. I can see when they come back from Unpickler
they are wrong, but I can't find where they get created or where they get pickled.