The docs tell me to send an HTTP-formatted date (without telling me quite
what that is). It reads like I should be able to pass something like "Fri
Dec 1 12:00:00 +0000 2006" (which was before my first ever tweet). But no
matter what date I send, I always get the most recent tweets back. The
count param works, but if I make it too large (e.g., 2000), I get an
urllib2.HTTPError: HTTP Error 502: Bad Gateway.
Thanks for any help.
Terry
Yeah, the twitter API is a little weird there. Try using the 'page'
parameter as well as 'since' and 'count'.
The API sends you the most recent 'count' statuses which are more recent
than 'since' (or 'since_id'). If you set 'page' greater than 1, it will
skip the most recent (page-1)*count statuses to find a group to return.
Last time I checked the API, 'count' could not exceed 200.
Marc> Excerpts from Terry Jones's message of Sun Jun 14 20:53:52 -0400 2009:
>> Does the 'since' param in twitter.Api.GetUserTimeline do anything? I
>> tried pulling back some old tweets, but the param seems to be ignored.
Marc> Yeah, the twitter API is a little weird there. Try using the 'page'
Marc> parameter as well as 'since' and 'count'.
Hi Marc.
Thanks for the reply. GetUserTimeline doesn't take a page argument,
though. (I'm looking at the Twitter Python code from the svn trunk).
Marc> Last time I checked the API, 'count' could not exceed 200.
It worked for me last night with 1500.
Terry
if max_id:
try:
parameters['max_id'] = int(count)
except:
raise TwitterError("max_id must be an integer")
should be int(max_id).
Terry
Terry
>>>>> "DeWitt" == DeWitt Clinton <dcli...@gmail.com> writes:
DeWitt> Fixed in trunk in r174. Please verify. Thanks!
DeWitt> http://code.google.com/p/python-twitter/source/detail?r=174
Shouldn't this better be a long()?
\Maex