[issue17584] collections.Iterator __subclasshook__ does not check if next() is callable

[Byron Ruth]

Byron Ruth added the comment:

Understood. I am not sure it is appropriate to follow-up with a question here, but would this be a downstream issue? My understanding of the iterator protocol is that is assumes the __iter__ and next methods are implements. In the example, the next method is defined as a property, but is still identified as an iterator. This seems an incorrect _behavior_ somewhere, although I may have assumed the incorrect place.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue17584>
_______________________________________