Ned Deily n...@acm.org added the comment:
I just ran into this problem on another platform. I believe the problem is due
to a sign-extension bug in the ncurses library unget_wch function (see link
below). It was apparently fixed in nurses 5.8; I've tested with the current
ncurses 5.9 and
John Bollinger john.bollin...@stjude.org added the comment:
The system on which I encountered the test failure uses ncurses 5.7, so that's
consistent with the theory that the test is tickling an ncurses bug.
I'll have a look at testing with ncurses 5.8, but it is not available from
RedHat or
John Bollinger john.bollin...@stjude.org added the comment:
Clarification: so that's not a good solution for most users ... of
RedHat-family distros, version 6.2 and earlier.
In fact, it looks like RedHat is sticking with its current version of ncurses
for RHEL 6.3, too, so no help is coming
John Bollinger john.bollin...@stjude.org added the comment:
Ok, I confirm that the test passes after the system's ncurses library is
upgraded to ncurses 5.8, and fails again when ncurses is downgraded back to
version 5.7.
--
___
Python tracker
New submission from John Bollinger john.bollin...@stjude.org:
I encountered this test failure while attempting to verify a patch for a
separate issue, and I found that it occurs with the unmodified source on the
default branch:
LD_LIBRARY_PATH=$PWD ./python -bb -Wd -m test -r -w -uall -v
