-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Django 4.1 #566
Comments
will relax the requirement and try to push a new release |
+1 |
Any updates? |
work in progress #567 |
I'm going to do the same on the testing front |
Is there still something preventing django-celery-beat from supporting Django 4.1? |
Please merge #589 to allow support for Django 4.1 |
@carlosdorneles-mb #567 only updated test requirements from what I can tell. Install requirements are still behind (see the diffs in my PR). If you try to install from master branch right now it will downgrade Django to 4.0.x. |
#581 can anyone check the python 3.7 failures? |
@auvipy Upstream error by kombu & celery, caused by using importlib-metadata API which is deprecated at 5.0.0 Both libs have been fixed and merged but in 5.3.0 milestone. celery/kombu#1601 Only python < 3.8 needs importlib-metadata, which is why only python37 breaks here. open #591 to prove. |
@auvipy please release a version for django 4.1 support, which has multiple cve fixed. Would be glad to help if anything lack. |
yeah going to |
What is the estimate release date? |
released https://github.com/celery/django-celery-beat/releases/tag/v2.4.0 please try and report bugs |
Thanks for all that you all do! We appreciate ya! |
First, Thanks for this great project! 👍
Summary:
Current django-celery-beat requires Django (>=3.2.13,<4.1) and hence doesn't install together w/ Django 4.1.
The text was updated successfully, but these errors were encountered: