Allow consuming pickle message format for api#2
Open
haim0n wants to merge 2 commits intokodless:masterfrom
Open
Allow consuming pickle message format for api#2haim0n wants to merge 2 commits intokodless:masterfrom
haim0n wants to merge 2 commits intokodless:masterfrom
Conversation
kombu supports json as default, but pickle is popular option as well: https://docs.celeryproject.org/projects/kombu/en/stable/userguide/serialization.html
|
bump 😬 |
|
Can we merge this ? |
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
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.
kombu supports json as default, but pickle is popular
option as well:
https://docs.celeryproject.org/projects/kombu/en/stable/userguide/serialization.html
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: