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
Support premium search APIs #1175
Comments
I'm not a contributor yet but after a glance at the code it looks like a fairly simple change to make it possible and a bit more to make it easy. I might make a PR for this if nobody else is. Interestingly almost all of the code needed to do it appears to already be there |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Oh, so there is an issue about this already. I had started to just modify some existing code but got stuck at a |
I've created a branch (https://github.com/tweepy/tweepy/tree/premium-search) and draft PR (#1294) that adds API methods for the data endpoints of both premium search APIs. |
Coooool, nice one, thanks!! So how would I use this? I assume like that?
right? When I use Thanks! |
You can simply |
cool, thanks. |
@Harmon758 Thank you for developing a pull request for this. The cursor changes required to continue development have been merged, and I would be happy to see continued progress. |
I've added cursor support, and both methods should now be fully functional. |
Found what appear to be some bugs and missing features when using the search_30_day function in conjunction with paging. If you try to use a plus sign (+) in the query (i.e. for boolean searches), it crashes with the message "There were errors processing your request: no viable alternative at character '+'" -- I'm guessing a minus sign perhaps certain other characters would cause the same issue. Also, my original algorithm used tweet_mode='extended' as one of the parameters. As per Twitter, this allows for a full 280 character tweet to be returned, rather than truncating it to the original 140 character limit. It looks like this isn't supported by the new function. Here's the line in question:
And here's a sample query: bitcoin +btc |
I'm not sure what you mean by "for boolean searches", as As for extended Tweets, premium APIs are different from standard REST APIs and include an additional |
Hello, I would like to know what means |
I'm not sure where you're seeing that. |
Thanks for your reply. I.m glad to hear that. |
The Stale view on that page is simply GitHub showing all branches that no one has committed to in the last three months. |
This comment has been minimized.
This comment has been minimized.
Did this make it into 3.9.0? I don't see it listed in the release notes. |
v3.9.0 was released without #1294 having been merged yet. I had intended to release it with v3.9.0. |
just came across this and don't get how to include premium api support, since currently:
Any directions on how to proceed? |
The branch has been deleted since #1294 has been merged into the master branch. |
ok. pip install --upgrade git+https://github.com/tweepy/tweepy@master successfully installed. |
See the documentation for |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Don't forget to update tweepy with |
This comment has been minimized.
This comment has been minimized.
It seems that the premium search is still missing from the standard pip and conda installs with 3.10.0. The |
The premium search APIs were implemented with |
With recent API updates, both basic and premium accounts have access to full-history search as long as a development environment is created and specified by the API account holder. Will tweepy be able to access this feature sometime in the near future?
The text was updated successfully, but these errors were encountered: