-
Notifications
You must be signed in to change notification settings - Fork 247
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
warning ... YAMLLoadWarning ... deprecated #73
Comments
This was fixed in #68 - It's worth updating to the latest version on github, eg with pip:
|
Great, thanks. Why not / When deploy that to pypi ? Also, I might leave you again - because now actually tweepy is trying out ways to support the premium search, hooray. And I have plenty of tweepy code already so that might make it easier for me then. |
Oh, and now that I have your attention as someone at twitter ... what about these 2 suggestions:
|
For requests for new features this is the place to post them: https://twitterdevfeedback.uservoice.com/ (this is for API features, not UI) Or there's always https://twittercommunity.com/ For searching for retweets with comment, you need to use the Search API: tweepy/tweepy#1291 (comment) |
Thanks a lot for your suggestions, very helpful.
yes, I am aware of that - and I am looking into Premium search ... exactly for that. However, are you aware that I will be causing >3000 API calls instead of 1 ? I suggest you discuss how that can be avoided. Probably with a new API endpoint, no? |
That's a lot of calls to make, it will get very expensive with Premium - 5000 calls on |
Thanks a lot @igorbrigadir
Yes, I had though of that already. I don't quite understand the problem why I have to come up with such complicated (and expensive, as I learn now) workaround. Why not just give us an appropriate endpoint? Is there perhaps a political reason that I do not understand, to just not to provide one of these endpoints:
Especially the last one would save a LOT of queries, coding time, and money. Can you help me to understand WHAT exactly is the problem here? The twitter API is super amazing, and fun to work with - but this lack of functionality is almost a "bug-like flaw". Perhaps it's intended? But then ... why? |
This would be the perfect place for these ideas: https://twitterdevfeedback.uservoice.com/forums/921790-twitter-developer-labs |
VERY good idea, thanks for pointing that out to me. Let's see what happens. |
first time user here. I get this RED warning message:
when executing this code:
The text was updated successfully, but these errors were encountered: