`django.tasks` backend?

[RealOrangeOne]

I'm the author of the django.tasks DEP, and maintainer of django-tasks. To better flesh out many of the APIs, I built an RQ backend, to allow the django.tasks interface to back on to an RQ based queue and executor.

Currently, this implementation is being maintained inside the django-tasks package. Is there appetite to adopt this backend into the django-rq package? That way it can be more easily adopted (and discovered) by existing RQ users, and better maintained by those who know the RQ internals better than I.

[RealOrangeOne]

Update: The implementation now lives in its own package: https://github.com/RealOrangeOne/django-tasks-rq.

That shouldn't impact any potential upstreaming into django-rq, though.

[selwin]

@RealOrangeOne sorry for the late reply, just saw this message. Since the goal of this library is to allow Django projects to easily use RQ, I think it makes sense for django-rq to include a proper Django Task backend 😀

Does the upstreaming process mainly involve getting backend.py into django-rq?

[RealOrangeOne]

backend.py and associated tests, yes. I'd like to hope that by pulling the package in to django-rq that it gets a bit easier to maintain and work with. I've mostly dug around a few of the internal APIs myself to implement it, so it would also be interesting it being able to get a full review from people who understand the internals better to see if there are better ways of approaching things.

[selwin]

Will do. Let me do a v4 release this weekend and we can start porting it over here. Feel free to open a pull request whenever you're ready