@drevicko I don't see why iteration over search results should be any
different than any other timeline result. I've implemented an
MaxIdIterator in my fork of tweepy (pull request #282), which iterates
properly over any timeline. My solution doesn't assume any order in the
result set nor does it require additional fields in the JSON response from
twitter. Just working with timelines as instructed by Twitter in
https://dev.twitter.com/docs/working-with-timelines. Am I missing something?


On Sat, Jun 8, 2013 at 2:11 AM, drevicko <notifications@github.com> wrote:

> In tweepy/api.py:
>
> >      )
> > -    search.pagination_mode = 'page'
> > +    search.pagination_mode = 'search'
>
> while we're chaging things, perhaps it'd be better to set the pagination
> mode in bind_api(), since that's where it gets set in all other cases. We
> could pass search_api = True or pagination_mode = "search" to bind_api().
> We'd best be careful if "cursor" remains in allowed_param if we do this
> (as bind_api() will set pagination_mode = "cursor" in this case).
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/tweepy/tweepy/pull/248/files#r4600995>
> .
>