Message298280
| Author | r.david.murray |
|---|---|
| Recipients | Usui, amaury.forgeotdarc, andersk, eric.araujo, georg.brandl, pitrou, r.david.murray, rhettinger, terry.reedy, ysj.ray |
| Date | 2017-07-13.12:29:41 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1499948981.83.0.151554502042.issue8376@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I just had a colleague get confused about the container returning self, and he was referring to the iterator protocol docs at https://docs.python.org/3.6/library/stdtypes.html#iterator.__iter__. If you don't read that section with your thinking cap firmly in place it is easy to get confused about what "the iterator itself" means there. I think it would be beneficial to add a sentence about the iterator state needing to be independent for each iterator returned by the *container's* __iter__. A similar sentence in the tutorial might be all that is needed as well. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-07-13 12:29:42 | r.david.murray | set | recipients: + r.david.murray, georg.brandl, rhettinger, terry.reedy, amaury.forgeotdarc, pitrou, eric.araujo, ysj.ray, andersk, Usui |
| 2017-07-13 12:29:41 | r.david.murray | set | messageid: <1499948981.83.0.151554502042.issue8376@psf.upfronthosting.co.za> |
| 2017-07-13 12:29:41 | r.david.murray | link | issue8376 messages |
| 2017-07-13 12:29:41 | r.david.murray | create | |