Update from django-q to django-q2

[mrmurilo75]

It seems that development of django-q has become stale, so the dependencies are out-of-date (for example, redis 3.5.3 while latest if 5.2.1). Development has migrated to django-q2.

[mrmurilo75]

@adamspd I would like to try to implement this, but I'm not confident I could eval the implications of this change well without understanding the code. If you want to get in touch I would be glad to work together on it.

[adamspd]

Hi @mrmurilo75, sorry for the late response, I don't use django-q but django-q2 from the beginning. If you still want to work on other part of the project, I would be glad to explain some part of the code.

[ChloeLeitch]

This also means we can't use the email functionality of django-appointments with django 5 (as django-q uses deprecated packages from django 4) until django-q2 is used.

[adamspd]

django-q2 is the only one I've used; I haven't worked with django-q from the beginning. I noticed that django-q was not maintained (last commit was 4 years ago), and that django-q2 was a fork of the original project, so I read the documentation and used it instead. So, no worries there.

I will be closing this issue. Feel free to open a new one if you encounter any other problems or have questions related to the project.