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 very out of date versions, so any investigation has to keep that in mind  That has the consequence of significantly limiting the amount of help you can get because you're relying on people dredging up 4 years or so of memories.

Unfortunately, I don't know SQS.  If this is working fine with Rabbit as your broker, why the move to SQS while keeping all other dependencies the same?

On Saturday, October 26, 2019 at 4:33:23 PM UTC-4, Rogério Carrasqueira wrote:

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 2019 às 16:40, Jason <jjohn...@gmail.com> escreveu:
>
> 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 to the Google Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to django...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/419fedc2-a953-4a2f-a24e-560fbf3bd9ad%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6ab818d9-8129-45e4-9912-c297614535f5%40googlegroups.com.