[issue7096] test_curses fails on 3.1 when run under regrtest

Changes by R. David Murray : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7096] test_curses fails on 3.1 when run under regrtest

Sandro Tosi added the comment: mh, 3 months and no taker, let's close it? :) -- nosy: +sandro.tosi ___ Python tracker ___ ___ Python-b

[issue7096] test_curses fails on 3.1 when run under regrtest

R. David Murray added the comment: This still fails for me in the same way if I uncomment the skip. It works fine in py3k trunk, though, so unless someone wants to figure out what fix that wasn't backported fixed this, we could probably just close it as out of date. -- _

[issue7096] test_curses fails on 3.1 when run under regrtest

Stefan Krah added the comment: David, was this fixed in r75702 by any chance? Currently the test is just skipped in 3.1. -- nosy: +skrah ___ Python tracker ___ __

[issue7096] test_curses fails on 3.1 when run under regrtest

Mark Lawrence added the comment: Have any comments been made that could be referenced here? -- nosy: +BreamoreBoy ___ Python tracker ___ _

[issue7096] test_curses fails on 3.1 when run under regrtest

New submission from R. David Murray : test_curses currently fails on 3.1 when run under regrtest. It passes if run in verbose mode or standalone. The cause turns out to be that when not run in verbose mode regrtest substitutes an io.StringIO instance for sys.stdout, and that object does not hav