[issue7396] regrtest single: iterator not subscriptable

R. David Murray added the comment: Thanks for testing. Note that you don't need to use -s to run a single test. You can specify a list of tests to run on the regrtest command line, which can be just one test. -s for running all the tests one at a time so that you restart the interpreter betwe

[issue7396] regrtest single: iterator not subscriptable

James G. sack (jim) added the comment: Update: I was doing something wrong and getting false failures. I forgot to do ./configure and make after major revision-switches so the failures I was seeing in bz2 and codecs (and others, :-[ ) was bogus. Repeating the main message, though: The regrt

[issue7396] regrtest single: iterator not subscriptable

James G. sack (jim) added the comment: Thanks, it seems to work now. My test method uses the command format ./python -Ebb Lib/test/regrtest.py -s test_calendar Sorry for the delayed response, I discovered problems with test_bz2 test_codecs which I wanted to confirm was real rather than

[issue7396] regrtest single: iterator not subscriptable

R. David Murray added the comment: Yes, rebinding a variable to a different type is something that is considered an acceptable pattern in Python programs, at least in certain circumstances. Python programs generally use 'duck typing', and a list and an iterable have equivalent semantics for the

[issue7396] regrtest single: iterator not subscriptable

Changes by Ezio Melotti : -- nosy: +michael.foord, ncoghlan, pitrou, r.david.murray priority: -> normal versions: -Python 3.0 ___ Python tracker ___

[issue7396] regrtest single: iterator not subscriptable

New submission from James G. sack (jim) : file Lib/tests/regrtest.py Evidently rev 76260 (trunk) / 76261 (py3k) broke code at rev 76324 line 655 (py3k) rev 76321 line 620 (trunk) which is if tests[0] == alltests[i] because tests was rebound from a list to an iterable, and hence indexi