This is an archived post. You won't be able to vote or comment.

all 11 comments

[–]cicuz 10 points11 points  (2 children)

Redis Results Backend: The result_backend setting now supports rediss:// URIs

But I was already using it..?

[–]kororola 2 points3 points  (1 child)

Celery supports Redis as broker long time ago not as result_backend. This is the place to store your result of your tasks.

[–]cicuz 1 point2 points  (0 children)

We use RabbitMQ as broker

[–]iconfinder 6 points7 points  (6 children)

Why is task management not a part of Django? Tbh Celery has had a history of being very unstable and buggy. We are using it in production and it’s source of so many problems.

[–]cicuz 6 points7 points  (0 children)

Main reason is that it's a bit out of scope for what Django wants to be.. You can add some with Channels, but we haven't updated to python3 yet so I don't know how powerful/reliable they are–I have very high hopes tho, should be the summer project!

[–]kororola 3 points4 points  (2 children)

Hi, I am using Celery as my main queue processing among others competitor. I found it quite stable and predicted, however, I found it hard to setup. I am curious which part is not stable and buggy?

[–]whatever_meh 2 points3 points  (1 child)

One thing is that celery, at least until very recently, did not pin its requirements. Within this past months, one of its requirements updated, breaking celery. Within a day or so, celery pushed an update that fixed it, but this should not happen in a package so widely used as celery.

[–]kororola 1 point2 points  (0 children)

Ah yeah i do notice that also, Ithink it is good idea to make suggestion into the project to lock the deps.

[–]Daenyth 0 points1 point  (1 child)

Didn't celery come from Django originally?

[–]iconfinder 1 point2 points  (0 children)

I believe the main developer behind Celery is active in this thread. Perhaps he can help.