use session.deserialize to unpack message for rate limiting #5
Conversation
This file contains 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
rather than hardcoding json.loads Messages should **never** be deserialized by any means other than the Session API.
|
Ah interesting, I was doing this earlier but kept running into an error because I tried to deserialize the same message twice (duplicate signatures). I didn't think to change the base method like you do here. |
jdfreder
added a commit
that referenced
this pull request
Jan 21, 2016
use session.deserialize to unpack message for rate limiting
|
If need be, you could use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
rather than hardcoding json.loads, which fails on Python 3.5
Messages should never be deserialized by any means other than the Session API.