#celery

http://pastebin.com/YBJVdU0S anyone know how I can troubleshoot why its shutting down when loading tasks?

Popsikle: that ... is weird.

Is there a way you can execute some tasks sequentially, without passing the results of a task from one to another? I've got something like this. for x in list: chain(foo.s(...), bar.s(...))()

I'm wondering if there's some way I can do celery.execute_sequentially_somehow(*[chain(...) for x in list])

w0rp, maybe you could code that from a task sender perspective

waiting for the tasks to be done before sending the next

that sounds like your goal to me?

It's all because the second task does some junk with a Couch DB model in a codebase I only just started contributing to, which breaks if you try to access the model with tasks running in parallel.

It does some nonsense where it saves a count of things on the model after it finishes doing another thing.

I know if I start editing that so that is no longer the case (because it's dumb and wrong), I'll just get whining from the other developers.

Ah, I should be using .si instead of .s to do that. I get it.

Think I might have encountered a bug

the signals implementation uses id(sender) to filter the receivers

but according to the docs before/after_task_publish is supposed to work with the task name as sender

if you have a string stored in a variable, e.g. the djcelery scheduler PeriodicTask model

id(periodic_task.task) == id('that.task') is False