Message167105
To debug this issue, it would help to have the following information:
- locale encoding: encoding variable
- tested character: ch
- character read by ncurses: read
Can someone reproducing the issue try to add: print("encoding=%s, ch=%r, read=%r" % (encoding, ch, read)) before the error?
It may be an issue in the Python implementation of unget_wch() or get_wch().
--
> I believe the problem is due to a sign-extension bug in the ncurses library unget_wch function (see link below).
Can we workaround this issue in Python? For example, use value & 0xffffff?
--
The test should be modified to use the encoding of stdscr, not the locale encoding: encoding = stdscr.encoding. (In this test, both encodings should be the same.) |
|
Date |
User |
Action |
Args |
2012-08-01 09:28:50 | vstinner | set | recipients:
+ vstinner, georg.brandl, ned.deily, jcbollinger |
2012-08-01 09:28:50 | vstinner | set | messageid: <1343813330.83.0.378001775355.issue15037@psf.upfronthosting.co.za> |
2012-08-01 09:28:50 | vstinner | link | issue15037 messages |
2012-08-01 09:28:49 | vstinner | create | |
|