Tasks starting signal

[oliverhaas]

Really happy that this package (and the integration in django) is happening. 😄

I just skimmed over the codebase, and I noticed there is no "task starting/started" signal. I've missed such a signal in other task packages, so I'd thought it might be a good addition, and maybe an easy entry point to get involved and start working with django-tasks.

Just for illustration puposes and untested, here is basically what I mean put in code:
https://github.com/oliverhaas/django-tasks/pull/1/files

Does this make sense, or am I missing a good reason why many task libraries just have enqueue and finished signals?

[RealOrangeOne]

I think there was a reason I did this, I just forget what it was.

What do you see these signals being used for? Besides logging and observability? It's possible there'd be a way to use it to skip tasks (eg deduplication), but many other uses could lead to people just introducing more bugs.

It's not a No, not by a long shot. I'm just interested in the use case (mostly to avoid scope creep).

[oliverhaas]

Honestly it just is almost just logging, and occasionally a state update in some way. But logging gets quite extensive in some of our projects...

[RealOrangeOne]

It's not actually that complex, so even if just for the sake of completeness, I've added it #158

[oliverhaas]

Thanks! I would have been happy though to make a proper PR out of what I've posted.