-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
CRITICAL:root:twint.feed:Follow:IndexError #409
Comments
Very interesting thread, thanks for your quick reply. I'll see what I can do to make that happen, if it's not beyond my python knowledge |
That's a really interesting library! Thanks for sharing Feel free to provide any kind of patch, either by code or concept! |
Has anyone found a solution for this? I get this error after fetching just 20 usernames. |
Hi, just wondering if I resume the scrape, am i able start from where I stop? Since When I tried to resume the program, the scraped results would start over again. |
You have to specify |
I'm facing same issue, I'm getting this error, CRITICAL:root:twint.get:User:'NoneType' object is not subscriptable I'm running this command I'm getting above error after running the command with out getting any follower. |
I'm running the script on AWS EC2 Instance so I have also changes my IP but still getting this error,
I'm running above code. Total Followers are 1.9M but I'm receiving this error after 6 Lac followers. |
I am trying to extract the followers from a twitter account. I am getting the following error, it was working fine yesterday. |
That's because twitter killed the no js (mobile version) version of twitter on 15th December. Followers were scraped using that version. |
is there a new update? |
Same problem. Other twint features are working fine but I need this one |
The problem persists... |
So the whole lib is now useless? Nothing I try is working at the moment. |
Issue Template
Please use this template!
Initial Check
pip3 install --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint
;Command Ran
twint -u coindesk --followers --elasticsearch localhost:9200
Description of Issue
Got 30k results afterwards error:
CRITICAL:root:twint.feed:Follow:IndexError
Rerunning command doesn't give any immediate issues, just starts from 0 again
Environment Details
Ubuntu 18.04, Python 3.6, ES 7, kibana 7
The text was updated successfully, but these errors were encountered: