Support iteration with manually called next()

[igor-shevchenko]

Currently, if one calls next() method on tweet iterable, it raises exception, because _nextTweet is defined in __iter__(). I fixed it and also moved the check of __response existence to next(), so it raises 'No results available' exception, if there's no response.

[ckoepp]

Thanks a lot for the pull request.

I'll have a look at it and run the existing tests against it on the
weekend.
I'm pretty sure those will return green states and I can merge your
changes :)

On 2014-09-24 21:20, Igor Shevchenko wrote:

Currently, if one calls next() method on tweet iterable, it raises
exception, because _nextTweet is defined in __iter__(). I fixed
it
and also moved the check of __response existence to next(), so it
raises 'No results available' exception, if there's no
response.
You can merge this Pull Request by running:

git pull https://github.com/igor-shevchenko/TwitterSearch next

Or you can view, comment on it, or merge it online at:

#20

-- Commit Summary --

• move _nextTweet initialization to constructor
• Check existence of response in __next()

-- File Changes --

M TwitterSearch/TwitterSearch.py (6)

-- Patch Links --

https://github.com/ckoepp/TwitterSearch/pull/20.patch
https://github.com/ckoepp/TwitterSearch/pull/20.diff

---

Reply to this email directly or view it on GitHub:
#20