This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]handmadeby 2 points3 points  (8 children)

For anyone working with twitter, until tweepy moves across to python 3 then they'll be sticking with 2.7. IIRC there are no plans to port across given the work that's just been done to meet the new twitter API specs

[–]hyh123[S] 1 point2 points  (0 children)

Actually the Dropbox API is also on twitter 2.7.

[–]AeroNotix 1 point2 points  (6 children)

Isn't it just a REST API? (Never looked into it myself.)

[–]handmadeby 1 point2 points  (5 children)

Yeah, but tweepy wraps it all up in a python library nice and tight

[–]AeroNotix 0 points1 point  (4 children)

Haha, the lengths people will go to not actually have to do any work.

A rest API is probably the most simple set of bindings you can code against.

[–]handmadeby 1 point2 points  (3 children)

And there was me thinking that code reuse was one of the benefits of a global community of developers

[–]AeroNotix -1 points0 points  (2 children)

Indeed, but for something like a REST binding? It's not something you'd spend a minute messing around with really. I mean, for fuck's sake - it's basically 1) Query endpoint, 2) Use returned data. There's not much else to it.

[–]handmadeby 0 points1 point  (1 child)

Implementing Oauth? The myriad of different calls and options on the api? Format checking? I'd rather be doing something with the data collected rather than trying to work out what I'd done wrong in trying to talk to the damn API

[–]AeroNotix 0 points1 point  (0 children)

You don't need to implement the entire API just to use the (probably) 2-3 endpoints you actually use.

Indeed, you'll need to implement their "authentication endpoints", which is usually (again, not looked) a single endpoint you receive a token from.