[Josiah Carlson] >> I have written methods named 'next' which have *nothing* to do >> with the iterator protocol.
[Greg] >That would be another reason for renaming .next() to >.__next__() -- to avoid intruding on the user's >namespace. Another read is that iterators should be separate objects so that the namespace is coherent (with __iter__, next, and whatnot all being iterator related). Who is going to create a custon iterator that defines BOTH __next__ and next(), that would be less than ideal and not something we want to encourage. Raymond _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
