Update Celery supported features (Motivation/Compared to * update) #645
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smiling-watermelon
changed the title
spumer
reviewed
Jul 23, 2024
| | Redis support | Yes | Yes | Yes | Yes | | ||
| | | | | | | | ||
| +------------------------------+----------+-----------------+--------------+--------------+ | ||
| | In-memory broker support | Yes | No | Yes | No | |
There was a problem hiding this comment.
Kombu support :memory: broker and Celery support it as well
There was a problem hiding this comment.
I believe we can add dashboard support here too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some changes here are debatable, and, perhaps require additional review.
For example:
py2_cel- In the documentation it's not clear weather 4.2 here refers to the version of celery, or not. Because if it's maintained, then Python 2 is not dropped to this day, but this line was unchanged for 6 years now (according to Blame), and there were no releases to 4.. series of Celery since 2020.win- I guess leaving it at "No" is also correct, but Celerymay, ormay notwork on Windows.cel_rate- Support for rate limits is present all the way to version 3.1 (didn't look any further), so, perhaps it's stated as "No" because this is an extension.I would suggest a re-evaluation for all libraries in the table, though, and re-check Celery too.
Giving away this contribution in hopes to push the metaphorical stone on the matter of outdated comparisons.