Allow kwargs for fetch_request_token and fetch_access_token to be passed to requests.session #226
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
… oauth1_session to be passed to post-method of requests.session
|
This looks good to me, thank you! ✨ 🍰 ✨ |
Lukasa
added a commit
that referenced
this pull request
Feb 19, 2016
Allow kwargs for fetch_request_token and fetch_access_token to be passed to requests.session
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 was basically suggested in the comments of #149. As i can't commit to this open pull request i make a new one.
Allow users to pass kwargs to fetch_request_token and fetch_access_token that are then passed to the post method of requests.session.
I need this for disabling SSL-verification for certain calls. But I don't think it makes sense to implement every possible parameter individually.