Remove the "strict" parameter of http.client for Python 3.4+ compatability #34
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
…ility Signed-off-by: Huang Le <4tarhl@gmail.com>
|
Does this mean python-bitcoinrpc is Python 3 compatable? If so I'll update the README. |
Author
|
@addisonamiri Yes, after the change made in this PR, I've used it for several weeks without any problem. |
Contributor
|
It appears that python-bitcoinrpc won’t be fully Python 3 compatible until #39 is merged. |
Closed
Owner
|
Superceded - please check tip and see if further changes are needed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
The http.client class has obsoleted the parameter 'strict' since Python 3.4, adopt this change in our AuthServiceProxy class to be compatible.
Signed-off-by: Huang Le 4tarhl@gmail.com