Re: for loop + transaction.on_commit + celery = Unexpected Behaviour

2021-12-03 Thread Martin Pätzold
This is an older topic, but for everyone who found this discusion and had the same issue: The problem is most likely using "lambda" inside a for-loop. If you switch out "lambda" for "functools.partial" it should work as expected. Jani Tiainen schrieb am Donnerstag, 27. April 2017 um 08:27:11 UTC

Re: for loop + transaction.on_commit + celery = Unexpected Behaviour

2017-04-26 Thread Jani Tiainen
Hi, I think your problem is to use POST['_models_changed']. Django uses specialized version of dictionary there which return _last_ value from list. You need to use special "get_list()" method to get whole list of objects. Your code should start working if you do data['_models_changed'].get

Re: for loop + transaction.on_commit + celery = Unexpected Behaviour

2017-04-24 Thread Emilio Jimenez Canalejo
The commit event handler is to commit a transaction, the on_commit event is for running a function when the commit is done. That is my intention, but maybe there is something I don't see. I want to execute a celery task, foo.delay(...), when the save of Model is finished. That way if I modify M

Re: for loop + transaction.on_commit + celery = Unexpected Behaviour

2017-04-24 Thread m712 - Developer
I'm not too familiar with Celery, but I think that for loop continuously keeps changing transaction's commit event handler. Maybe you are looking for something like transaction.commit instead of on_commit? On Apr 24, 2017 2:37 PM, Emilio Jimenez Canalejo wrote:Hi, I've been looking for some time a