Ronald Oussoren added the comment:
the test does get run with 'make buildbottest', and then fails with a
ValueError exception:
$ /Users/ronald/Projects/python/rw/default/tbuild/python.exe -W default -bb -E
-R -m test -r -w -j 1 -u all -W --timeout=3600 test_curses
Using random seed 2242495
[1/1] test_curses
test test_curses crashed -- Traceback (most recent call last):
File "/Users/ronald/Projects/python/rw/default/Lib/test/regrtest.py", line
1221, in runtest_inner
test_runner()
File "/Users/ronald/Projects/python/rw/default/Lib/test/test_curses.py", line
338, in test_main
main(stdscr)
File "/Users/ronald/Projects/python/rw/default/Lib/test/test_curses.py", line
324, in main
test_unget_wch(stdscr)
File "/Users/ronald/Projects/python/rw/default/Lib/test/test_curses.py", line
283, in test_unget_wch
read = chr(read)
ValueError: chr() arg not in range(0x110000)
That might be a bug in libcurses on OSX, I haven't tested with a separate
install of libcurses yet.
BTW. The patch mentioned in Issue12669 looks slightly bogus: as buildbot is a
daemon it might not even have a controlling tty. With some luck a proper fix
will require the explicit use of a pseudo-tty.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue15664>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
