I plan on utilizing: http://github.com/simplegeo/python-oauth2 for my
django-based Twitter app, however I'm wondering if anyone here who
understands the django example, understands it better than I do.
The first half of the page has an example for just plain Python, and
there's a part there, where it looks like the user is prompted for a
pin.
"oauth_verifier = raw_input('What is the PIN? ')"
However, lower in the page, in the Django example, there's no mention
of this.
Another difference between the two:
Python example: Uses: 'http://twitter.com/oauth/authorize'
Django: 'http://twitter.com/oauth/authenticate
Should I just ignore that, and just simply implement the Django
example into my code, and not try to fully understand that fully right
now? There's always later, for when I have time to really grasp the
Oauth2 flow.
My goal is to completely use "Use twitter as login", which I'm
guessing is the "three-legged" Oauth flow.
thanks,
Steve
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
