Larry Hastings <la...@hastings.org> added the comment: > OT, but since you brought it up: In my opinion, deprecating the > iterability of any builtin class is a horrible idea. It is a > Python feature, especially in 3.x, that all *are* iterable.
As you say, OT. But I don't see how it's a feature. Destructuring assignment is opaque (what was the order of fields again?), and with named attributes almost always unnecessary. And I find it hard to believe that there's a good use case for iterating over the values in a loop. I don't propose deprecating the iterability of these structures simply because I think it's inappropriate in a point release. But I hope to remove that misfeature in Python 4. (If you wish to continue the discussion, perhaps we should take it somewhere else?) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15118> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
