議論： Iterables versus iterators: the protocol behind for loops

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

翻訳がないため、原文を表示しています。 原文

For the last pitfall, the `collections.abc` documentation is explicit that `isinstance(x, Iterable)` does not detect classes iterable only through `__getitem__`, and states that the only reliable way to determine whether an object is iterable is to call `iter(obj)`; a boundary check that wants to reject non-iterables should therefore call `iter()` (and catch `TypeError`) rather than test the ABC. On 'materialise once with `list(xs)`': `itertools.tee()` is the alternative when the input is large and both passes are incremental, but it buffers every item between the slowest and fastest cursor, so two passes that run one after the other make it hold the whole sequence anyway and `list()` is cheaper and clearer. For annotations, a generator function that is only iterated should be typed `Iterator[T]`; `Generator[Y, S, R]` is for callers that `send()` or use the return value.