-
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
Django>=3.2,<4.2 #567
Django>=3.2,<4.2 #567
Conversation
Any update on this? |
The following patch works for me if it helps speed this up.
|
update this pleeeeeeeease ( |
At least when it comes to the CI, the failures are not related to Django bump and should be amended with the next release of |
any updates? |
Is this ready to go? |
What is the root issue here? Why have there been issues with the past two minor version bumps of Django? It shouldn't be taking weeks to just get |
We're also kinda stuck on Django 4.0 waiting for this PR. This also happened when Django 4.0 was released as far as I remember |
sphinx_celery already fixed at celery/sphinx_celery#40. sphinx_celery warning should disappear after rerun. Try to solve py39-flake8 error first at #583 |
@auvipy can you take a look? LGTM analysis failed for some unknown reason. I think rerun will work? (since last commit LGTM looks happy) Hope it's not because I merge into dj42 branch instead of main :( |
How can it take more then 2 months to update the requirements. Please fix this! |
No description provided.