Message163609
| Author |
larry |
| Recipients |
Arfrever, eric.araujo, jcea, larry, serhiy.storchaka, terry.reedy |
| Date |
2012年06月23日.13:45:00 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1340459101.86.0.295071450624.issue15118@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> 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?) |
|