This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Trundle, vstinner
Date 2009-08-27.22:31:54
SpamBayes Score 4.01159e-10
Marked as misclassified No
Message-id <>
First, make sure that your Python3 build uses libncursesw and not
libncurses, because libncursesw supports unicode, whereas libncurses
doesn't... On UNIX, use the following command to check this:

ldd $(./python -c "import _curses; print(_curses.__file__)")|grep curses

> Note that the output here always seems to be utf-8, 
> which is plain wrong.

Yes, addstr() always uses utf8 to convert unicode to bytes. It's wrong
if the terminal uses a different charset. But I'm not sure that using
bytes is a better idea: since you would like to print characters,
unicode is the right type.

An idea would be to use a configurable charset. Eg. add a 'charset'
attribute to a window (or to the module).
Date User Action Args
2009-08-27 22:31:56vstinnersetrecipients: + vstinner, Trundle
2009-08-27 22:31:56vstinnersetmessageid: <>
2009-08-27 22:31:55vstinnerlinkissue6745 messages
2009-08-27 22:31:54vstinnercreate