-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Treat IncompleteRead as a disconnect or timeout, and reconnect. #498
Conversation
0246abf
to
c841a09
Compare
Treat IncompleteRead as a disconnect or timeout, and reconnect.
I installed latest version from tweepy but I am still getting IncompleteRead(0 bytes read, 287 more expected)', IncompleteRead(0 bytes read, 287 more expected)) |
Me too!
|
I'm having the same problem with Tweepy 3.5.0 |
yeah, just encountered this issue yesterday. Any news or updates on this? |
This should handle both cases of incomplete read catched by requests, or catched by tweepy. This resolves tweepy#237, resolves tweepy#448, resolves tweepy#536, resolves tweepy#650, resolves tweepy#691, resolves tweepy#798. Similar to tweepy#498.
Bug still exists |
can you try pip install tweepy --upgrade this worked for me |
I'm having the same problem with the last version! |
Fix for #18, #92, #237, #242, #448.