Skip to content
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

start-time end-time arguments having no effect #151

Open
networks1 opened this issue May 19, 2022 · 2 comments
Open

start-time end-time arguments having no effect #151

networks1 opened this issue May 19, 2022 · 2 comments
Labels

Comments

@networks1
Copy link

Describe the bug
tweets are being returned that fall outside the start-time and end-time arguments. Call below returned tweets back to 2011

To Reproduce
/usr/local/bin/search_tweets.py --query "istandwithrussia OR istandwithputin" --filename-prefix ~/standwith.json --no-print-stream --start-time "2022-02-20 00:01" --end-time "2022-05-17 13:52" --expansions=author_id,entities.mentions.username,geo.place_id,in_reply_to_user_id,referenced_tweets.id,referenced_tweets.id.author_id --tweet-fields=id,author_id,created_at,text,geo,entities --user-fields=location,description,public_metrics,username --results-per-call=500

Expected behavior
Tweets returned that have created_at attribute between the specified dates.

Environment
Ubuntu 20.04
Python version 3.6

Additional context
I am an academic API user and this may be defaulting to historical search, but don't know if there is a way to tell or specify otherwise.

@networks1 networks1 added the bug label May 19, 2022
@igorbrigadir
Copy link

The time and date format has to be YYYY-mm-DDTHH:MM so,

--start-time "2022-02-20 00:01" --end-time "2022-05-17 13:52"

should be

--start-time "2022-02-20T00:01" --end-time "2022-05-17T13:52"

(all these are UTC)

@networks1
Copy link
Author

networks1 commented May 19, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants