I modified my destroyStatus based script to make a pause of 3 seconds
between all call to the twitter api.
the rate limit status show 136 150 but my script fail after the first
destroyStatus.
Traceback (most recent call last):
File "search_results.py", line 11, in <module>
twitter.destroyStatus(int(machin['id']))
File "/Users/roland/Development/twitter/twython/twython.py", line
494, in destroyStatus
raise TwythonError("destroyStatus() failed with a %s error code."
% `e.code`, e.code)
File "/Users/roland/Development/twitter/twython/twython.py", line
40, in __init__
raise APILimit(msg)
twython.APILimit: 'destroyStatus() failed with a 400 error code.'
Frédéric
it seems that every call to destroyStatus return a 400 error.
I placed my call to destroyStatus in a try/except and ignoring the
false error.
Also it seems that call to destroyStatus are not counted in the rate
limit.
I think that only the calls to getUserTimeline are counted then
destroyStatus are "free" but return a 400 error.
Frédéric
Le 31-août-09 à 01:58, Frédéric Roland a écrit :
> I modified my destroyStatus based script to make a pause of 3
> seconds between all call to the twitter api.
> the rate limit status show 136 150 but my script fail after the
> first destroyStatus.
>
...
> twython.APILimit: 'destroyStatus() failed with a 400 error code.'
I think that this is may be what is a known issue with the Twitter API
right now. Try accessing the destroyed Status after a 400 message to
see if the call succeeded despite the error response.
White listing is said to normally take 1 week but has been reported at
2 weeks since the DDoS attacks at the beginning of the month.
Chris Babcock