On Fri, 10 Feb 2006, "Martin v. L?wis" wrote:
Martin Michlmayr wrote:
Martin, can you please look into this?
Thomas is right: Python sets the locale first to "", then back
to "POSIX". This is intentional: it tries to obtain the CHARSET
during startup, but wants to leave locale control to the script.
ok. It was a little surprising to see it switch back.
(presumably python scripters are used to this behavior)
So the test script has a bug: it should explicitly perform
setlocale (if ncurses requires that for proper operation).
I'll attach the corrected test script.
I then manually tried to link _curses.so with ncursesw,
and tried running the script, with no success. Investigating
further, it turns out that python links with readline,
and readline links with ncurses, not ncursesw. For some
readline is using ncurses' termcap interface.
ncursesw presents the same interface, so there would be no adverse
impact by loading only one of ncurses/ncursesw.
I also noticed that the build process linked _curses.so against a static
library (libncursesw.a) in preference to the libncursesw.so (which is
probably not the intended behavior).
reason, it is only svn trunk Python which links with
readline, not Debian python, so there is hope.
Regards,
Martin
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
