Added oauth_verifier arg #162
No reviewers
Labels
No labels
Bug
Enhancement
Feature Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: code/twython#162
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Since Twitter now enforces OAuth 1.0a the
oauth_verifierattached to thecallback_urlhas to be passed to final authentication viaGET. Added a new arg for this.This is the more correct way. +1
The
oauth_verifiershould not be passed through theinit; instead it should be passed through theget_authorized_tokensmethod:Because it's only used in that case?
@simondlr Correct.
@hansenrum Thank you, merging now! I'll push a release sometime today or tomorrow, I have another change I want to add too.
minor point: you might wanna change the example used in the documentation accordingly.
Thank you, I'll get on that in master branch!
Sent from my iPhone
On Apr 6, 2013, at 3:06 AM, Falcon Dai notifications@github.com wrote:
Can you please update the package in PIP? The change for this isn't in the version thats up there
Yes, a PyPi update would be much appreciated!
You guys!! 😊 haha
I'll push an update within the hour!
Twython2.7.1 is now available via PyPi!pip install -I twythonI don't understand where you obtain the oauth_verifer...
@leopoldsg it comes in a GET variable called "oauth_verifier" when Twitter redirects to your callback URL after the user authorizes your app. You need to grab it from the request when handling your callback URL.
so what code would you write for that get request?
requests.get('callbackurl')?
Authorization URL
Be sure you have a URL set up to handle the callback after the user has allowed your app to access their data, the callback can be used for storing their final OAuth Token and OAuth Token Secret in a database for use at a later date.
Handling the callback
Then you'd store
in a database or something