-
-
Notifications
You must be signed in to change notification settings - Fork 314
Description
I have been using library a lot and was a bit concerned that it hasn't been updated in over a year. Therefore, I have created a fork in which I have merged a few of the current open PRs. I have also pushed a few patches myself.
The new repo/package: https://github.com/GDay/django-q2.
It's compatible with django-q, you don't need to change any code to make this work. Just swap the libraries.
What I have done so far:
- Updated all dependencies. Dropped support for Django 2.2 (it should still work though) and added support for the newer Python versions and Django 4.1.x.
- Removed Disque as it's outdated and now part of Redis as a submodule instead.
- I have removed the
Arrow,RedisandBlesseddependency. It currently only needsdjangoanddjango-picklefieldto work.- If you need the monitor commands, then you will need to install
Blessedas well.
- If you need the monitor commands, then you will need to install
- Merged refactor: show function name as it runs #677 to show function name in the logs as it runs (next to the unique id/human hash)
- Moved from Codecov to coveralls. Codecov tends to fail quite often at random, while coveralls has been very stable.
- Moved the docs to https://django-q2.readthedocs.io (and updated them)
- Merged turkish translation added #674 which adds Turkish translations
- Automated publishing to pypi.
- Merged Fix connection issues with CONN_MAX_AGE > 0 #604 to fix a connection issue
- Merged Replace use of eval() by ast.parse() + ast.literal_eval() #603 to fix a potential security issue
- Merged Admin improvements #605 to improve the admin area
- Merged Save limit per group/func/name #687 to improve saving tasks
- Made testing a lot easier with docker-compose
And perhaps a few more things that I forgot.
There are a few more bugs that I have encountered with Django Q that I am going to solve over the next few days and I plan to keep the Q2 library up to date for the foreseeable future. I am also open to adding a few collaborators to make sure the project stays alive.
Also, it looks like Ilan (the author of this project) has replied a few times in this thread: #664. If this project does indeed get brought back to life in the near future (with more maintainers), then I am happy to archive my repo and create PRs for the changes that I have made myself back to this project.
Let me know if there are any questions.