[issue26492] Exhausted array iterator should left exhausted

2016-03-31 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue26492] Exhausted array iterator should left exhausted

2016-03-08 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: TODO: After resolving issue26494 add similar test for array. -- ___ Python tracker ___

[issue26492] Exhausted array iterator should left exhausted

2016-03-08 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Thanks Victor. Answered you comments. -- ___ Python tracker ___ ___

[issue26492] Exhausted array iterator should left exhausted

2016-03-08 Thread STINNER Victor
STINNER Victor added the comment: I reviewed exhausted_array_iterator2.patch. -- nosy: +haypo ___ Python tracker ___

[issue26492] Exhausted array iterator should left exhausted

2016-03-08 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Thanks for suggestion Benjamin. seq_tests.py provides common tests for list, tuple, UserList and deque. This test doesn't work for tuple, since it is not mutable. It doesn't work for deque, since it can't be iterated after changing size. Common test for

[issue26492] Exhausted array iterator should left exhausted

2016-03-07 Thread Benjamin Peterson
Benjamin Peterson added the comment: Can you add just one patch to seq_test.py? -- ___ Python tracker ___ ___

[issue26492] Exhausted array iterator should left exhausted

2016-03-06 Thread Serhiy Storchaka
New submission from Serhiy Storchaka: There is general rule that after raising StopIteration the iterator should always raise StopIteration even if new data is added to iterating sequence. Array iterators don't obey this rule. Proposed patch makes array iterator to left in exhausted state