lookup_user #255

Closed
opened 2013-08-05 20:54:37 -07:00 by AndreiDev · 1 comment
AndreiDev commented 2013-08-05 20:54:37 -07:00 (Migrated from github.com)

Hi!

If I'm not mistaken you used a GET method to implement the "lookup_user" api.
On the twitter/doc page they say:
"You are strongly encouraged to use a POST for larger requests"

Will it be OK to simply change the endpoints.py file like so (post instead of get)? :

def lookup_user(self, **params):
return self.post('users/lookup', params=params)

Thanks, Andrei.

Hi! If I'm not mistaken you used a GET method to implement the "lookup_user" api. On the twitter/doc page they say: "You are strongly encouraged to use a POST for larger requests" Will it be OK to simply change the endpoints.py file like so (post instead of get)? : def lookup_user(self, **params): return self.post('users/lookup', params=params) Thanks, Andrei.
michaelhelmick commented 2013-08-06 08:51:50 -07:00 (Migrated from github.com)

You could issue a Pull Request for that change!

You could issue a Pull Request for that change!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: code/twython#255
No description provided.