Re: Celery with SQS

celery 4.x is for django 18 or newer Thing is, there's been *a lot* of changes in django since 1.4, which last recieved a minor update in 2015. I get updating is not as easy as waving a magic wand, but you're using

Re: Celery with SQS

Hi issuer, please check: Warning If you import models directly rather than using the historical models, your migrations *may work initially* but will fail in the future when you try to re-run old migrations (commonly, when you set up a new installation and run through all the migrations to set u

Re: Celery with SQS

Hello Jason! Thanks for your reply, it is not so easy to move from 1.4.22 to 2.2, it a big leap. I can upgrade the celery to 4.3, but I don't know if it will work well with Django 1.4.22. Do you have a clue about what could be this issue? Thanks Rogério Carrasqueira Em sáb, 26 de out de 201

Re: Celery with SQS

both those versions are severely out of date, so I would first suggest to update. current version of celery is 4.3, and django is 2.2. If you have reasons to move from rabbit to SQS, why not update everything else while you're at it? -- You received this message because you are subscribed t

Celery with SQS

Hello All! I'm using Celery 3.1 with Django 1.4.22 and I want to move from RabbitMQ to SQS. I've setup the celery and all scheduled tasks are running as well. But when I have to use the method add_consumer, the jobs are not consumed by the worker and no response from then. See what I'm doing: >>>