diff options
author | Sol Jerome <sol.jerome@gmail.com> | 2011-04-09 14:27:56 -0500 |
---|---|---|
committer | Sol Jerome <sol.jerome@gmail.com> | 2011-04-09 14:27:56 -0500 |
commit | 246557f31b1be5d73419434e2f05f7a7653de592 (patch) | |
tree | 91790049f6bf7d142f677c72623d5256ebdf0cf8 /testsuite | |
parent | 227690fca43d08f1c6cc9d19afc1013fe8f3eec0 (diff) | |
download | bcfg2-246557f31b1be5d73419434e2f05f7a7653de592.tar.gz bcfg2-246557f31b1be5d73419434e2f05f7a7653de592.tar.bz2 bcfg2-246557f31b1be5d73419434e2f05f7a7653de592.zip |
Reports: PY3K compatibility fix for PEP 3114
Quoted from PEP 3114:
The iterator protocol in Python 2.x consists of two methods:
__iter__() called on an iterable object to yield an iterator,
and next() called on an iterator object to yield the next item in
the sequence. Using a for loop to iterate over an iterable object
implicitly calls both of these methods. This PEP proposes that the
next method be renamed to __next__, consistent with all the other
protocols in Python in which a method is implicitly called as part
of a language-level protocol, and that a built-in function named
next be introduced to invoke __next__ method, consistent with the
manner in which other protocols are explicitly invoked.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
Diffstat (limited to 'testsuite')
0 files changed, 0 insertions, 0 deletions