> An alternative approach would be to raise an exception when calling > iter() on an exhausted iterator. This is orthogonal to whatever > .next() does on such and iterator. This just adds more complicated rules to no avail. iter() on an iterator should return that iterator itself. The state of that iterator is what it is. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4