[PATCH] MaximumHitFrequency returns 0 when requests are maxed out

danielpronych / python-twitter

Automatically exported from code.google.com/p/python-twitter

Apache License 2.0

0 stars 0 forks source link

[PATCH] MaximumHitFrequency returns 0 when requests are maxed out #187

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Max out Twitter rate.
2. Invoke MaximumHitFrequency.

What is the expected output? What do you see instead?

It returns 0.
Expected result: time until next rate limit reset.

Original issue reported on code.google.com by edward.h...@gmail.com on 10 Feb 2011 at 8:03

GoogleCodeExporter commented 8 years ago

Fixed patch.

Original comment by edward.h...@gmail.com on 20 Feb 2011 at 4:10

Attachments:

0001-MaximumHitFrequency-don-t-return-zero.patch

GoogleCodeExporter commented 8 years ago

Original comment by bear42 on 20 Feb 2011 at 10:15

Changed state: Accepted

GoogleCodeExporter commented 8 years ago

committed changeset 225:7f86ea33e2fa

Original comment by bear42 on 27 Feb 2011 at 4:52

Changed state: Fixed