Update README to Include FastAPI in Framework Integration Section #8978
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.
Note: Before submitting this pull request, please review our contributing
guidelines.
Description
This Pull Request updates the "Framework Integration" section of the README to include FastAPI, a popular (> 70.9k ⭐) and fast-growing asynchronous web framework. This addition reflects Celery's compatibility with FastAPI and indicates to users that no special integration package is needed to use Celery with FastAPI.
Changes Made:
Added a new row in the integration table for FastAPI, marked as "not needed" for any special integration package. This aligns with the entries for other frameworks like Django and Flask where no specific Celery integration package is required.
--
This update ensures the README remains current and informative, particularly for developers exploring asynchronous frameworks compatible with Celery. By explicitly listing FastAPI, we aim to assist in clearer framework choices for Celery users, especially given FastAPI's growing popularity and frequent use in modern web applications.