mysql-replication support for PyMySQL>0.10.0 was introduced in v0.22 #144
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
|
thanks, I'm merging the PR. |
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.
This might not be the way to safeguard against it, but for illustration, my upgrade of pg_chameleon to 2.0.18 pulled in version
0.21ofmysql-replicationand0.10.1ofPyMySQLThis resulted in
charset_to_encodingerrors which were addressed in version 0.22 ofmysql-replication.A manual bump of
mysql-replication==0.22fixed this for me.If the requirement could be expressed in the package that would be nice.