mirror of
https://github.com/adambard/learnxinyminutes-docs.git
synced 2024-12-23 09:41:36 +00:00
[python3/en] Use next()
instead of __next__()
Fixes issue #1148. The reasoning is well explained by the issue. One can also refer to the docs [0], showing it is more idiomatic to use `next()`. [0]: https://www.python.org/dev/peps/pep-3114/ #double-underscore-methods-and-built-in-functions
This commit is contained in:
parent
bd998e10a8
commit
ac2dfe7dc7
@ -394,15 +394,15 @@ our_iterable[1] # Raises a TypeError
|
||||
our_iterator = iter(our_iterable)
|
||||
|
||||
# Our iterator is an object that can remember the state as we traverse through it.
|
||||
# We get the next object by calling the __next__ function.
|
||||
our_iterator.__next__() #=> "one"
|
||||
# We get the next object with "next()".
|
||||
next(our_iterator) #=> "one"
|
||||
|
||||
# It maintains state as we call __next__.
|
||||
our_iterator.__next__() #=> "two"
|
||||
our_iterator.__next__() #=> "three"
|
||||
# It maintains state as we iterate.
|
||||
next(our_iterator) #=> "two"
|
||||
next(our_iterator) #=> "three"
|
||||
|
||||
# After the iterator has returned all of its data, it gives you a StopIterator Exception
|
||||
our_iterator.__next__() # Raises StopIteration
|
||||
next(our_iterator) # Raises StopIteration
|
||||
|
||||
# You can grab all the elements of an iterator by calling list() on it.
|
||||
list(filled_dict.keys()) #=> Returns ["one", "two", "three"]
|
||||
|
Loading…
Reference in New Issue
Block a user