https://github.com/bear/python-twitter
Revision 9dc54923ad4e318237c9406841ebac63f2903e7c authored by Jeremy Low on 17 February 2016, 02:53:40 UTC, committed by Jeremy Low on 17 February 2016, 02:54:43 UTC
The idea is that if you are making a call to, say, ``/statuses/lookup.json`` and the limit information is stale, i.e., limit.reset is in the past, then you should make another call to ``/application/rate_limit_status.json`` to get your new limits and reset. That said, this could result in a lot of hits to *that* endpoint, thereby rate limiting your application on the ``/application/rate_limit_status.json`` endpoint and causing unnecessary sleeps for the API. Worst case scenario is that your application calls a bunch of different methods hitting a bunch of different endpoints and you end up making a ton of checks on rate_limit_status.json and, since ``Api.InitializeRateLimit()`` does not abide by rate limits, you could get blacklisted.
1 parent c5d66cf
Tip revision: 9dc54923ad4e318237c9406841ebac63f2903e7c authored by Jeremy Low on 17 February 2016, 02:53:40 UTC
removes check on reset time.
removes check on reset time.
Tip revision: 9dc5492
| File | Mode | Size |
|---|---|---|
| doc | ||
| examples | ||
| testdata | ||
| tests | ||
| .gitignore | -rw-r--r-- | 363 bytes |
| .travis.yml | -rw-r--r-- | 234 bytes |
| AUTHORS.rst | -rw-r--r-- | 701 bytes |
| CHANGES | -rw-r--r-- | 21.5 KB |
| COPYING | -rw-r--r-- | 605 bytes |
| LICENSE | -rw-r--r-- | 11.1 KB |
| MANIFEST.in | -rw-r--r-- | 93 bytes |
| Makefile | -rw-r--r-- | 901 bytes |
| NOTICE | -rw-r--r-- | 109 bytes |
| README.rst | -rw-r--r-- | 6.3 KB |
| coveragerc | -rw-r--r-- | 23 bytes |
| get_access_token.py | -rwxr-xr-x | 2.7 KB |
| python-twitter.spec | -rw-r--r-- | 1.1 KB |
| requirements.testing.txt | -rw-r--r-- | 44 bytes |
| requirements.txt | -rw-r--r-- | 34 bytes |
| setup.cfg | -rw-r--r-- | 127 bytes |
| setup.py | -rwxr-xr-x | 2.1 KB |
| test.py | -rw-r--r-- | 152 bytes |
Computing file changes ...
