You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the pip version but the code in my stacktrace does not appear to have changed since then. It appears as if a simple sleep on the error would have fixed the problem but I was under the impression it was already doing that. The program was running for 6-12 hours before it crashed. I do not know if this is a bug or If there is a way to handle the error and have it resume easily.
JakeWarden done
Traceback (most recent call last):
File "/Users/zacharyrothberg/PycharmProjects/twitterbotffs/MainBot.py", line 34, in<module>
profilenewaccounts(accounts)
File "/Users/zacharyrothberg/PycharmProjects/twitterbotffs/MainBot.py", line 25, in profilenewaccounts
data = api.GetFollowerIDs(screen_name=item)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/twitter/api.py", line 2464, in GetFollowerIDs
total_count=total_count)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/twitter/api.py", line 2412, in _GetFriendFollowerIDs
count=count)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/twitter/api.py", line 2290, in _GetIDsPaged
data = self._ParseAndCheckTwitter(resp.content.decode('utf-8'))
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/twitter/api.py", line 4894, in _ParseAndCheckTwitter
self._CheckForTwitterError(data)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/twitter/api.py", line 4914, in _CheckForTwitterError
raise TwitterError(data['errors'])
twitter.error.TwitterError: [{'message': 'Rate limit exceeded', 'code': 88}]
The text was updated successfully, but these errors were encountered:
This is usually something going on with Twitter and their edge servers returning inconsistent rate limits. See issue #350 . We try as best we can, but I'd suggest a try: / except block around your function if this is going to be a long-running operation.
I am using the pip version but the code in my stacktrace does not appear to have changed since then. It appears as if a simple sleep on the error would have fixed the problem but I was under the impression it was already doing that. The program was running for 6-12 hours before it crashed. I do not know if this is a bug or If there is a way to handle the error and have it resume easily.
and here is the stack trace
The text was updated successfully, but these errors were encountered: