Well, I don't mind doing it either way, but I think the more likely use
cases to reach the rate limits are ones that use cursors and in these cases
it makes sense to wait or get an exception. If you come up with a use case
that needs to monitor the rate limit and doesn't involve a cursor then I'm
happy to implement it.
On Mar 13, 2014 2:56 PM, "Aaron1011" <notifications@github.com> wrote:

> In tweepy/binder.py:
>
> > @@ -155,15 +167,31 @@ def execute(self):
> >                      resp = conn.getresponse()
> >                  except Exception, e:
> >                      raise TweepError('Failed to send request: %s' % e)
> > -
> > +
> > +                if self.wait_on_rate_limit:
>
> @nirg <https://github.com/nirg>: Shouldn't we always store the remaining
> calls and time until reset? Even if Tweepy doesn't sleep, it might be
> useful to be able to get the number of calls remaining?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/tweepy/tweepy/pull/390/files#r10580177>
> .
>