←back to thread

Django: what’s new in 6.0

(adamj.eu)
379 points rbanffy | 1 comments | 09 Dec 25 20:33 UTC | HN request time: 0.263s | source
Show context
teagee ◴[09 Dec 25 21:37 UTC] No.46211038[source]▶
Any code or blog written by Adam is worth spending some time on.

It will be interesting to see how the tasks framework develops and expands. I am sad to see the great Django-Q2 lumped in with the awful Celery though.

replies(9): >>46211810 #>>46212076 #>>46212142 #>>46212219 #>>46212861 #>>46215681 #>>46215766 #>>46216187 #>>46217127 #
1. boxed ◴[10 Dec 25 09:26 UTC] No.46215766[source]▶
I tried django-q and I thought it was pretty terrible. The worst was that I couldn't get it to stop retrying stuff that was broken. Sometimes you ship code that does something unexpected, and being able to stop something fast is critical imo.

Fundamentally I think the entire idea behind celery and django-q is mostly misguided. People normally actually need a good scheduler and a bring-your-own queue in tables that you poll. I wrote Urd to cover my use cases and it's been rock solid.