Message340253
| Author | yan12125 |
|---|---|
| Recipients | xdegaye, yan12125 |
| Date | 2019-04-15.09:55:52 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1555322152.91.0.760294838917.issue36630@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
I asked on bug-ncurses mailing list and Thomas Dickey suggests "improving the python curses binding to handle the newer terminal descriptions". Looks like that requires non-trivial efforts. On the other hand, I've also found a workaround: $ TERM=xterm python -m test -u curses -v test_curses (or anything without -256color suffix for $TERM) How about setting TERM=xterm in tests and documenting that CPython does not support new terminal descriptions for now? [1] http://lists.gnu.org/archive/html/bug-ncurses/2019-04/msg00003.html |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-04-15 09:55:52 | yan12125 | set | recipients: + yan12125, xdegaye |
| 2019-04-15 09:55:52 | yan12125 | set | messageid: <1555322152.91.0.760294838917.issue36630@roundup.psfhosted.org> |
| 2019-04-15 09:55:52 | yan12125 | link | issue36630 messages |
| 2019-04-15 09:55:52 | yan12125 | create | |