homepage

Because of #7384, Python3 now links _curses.so to ncurses library (bytes version) instead of ncursesw library (unicode version) if readline is linked to ncurses. I'm using Linux (Debian Sid).
On Linux, Python3 should maybe only link to the unicode version, because the bytes version has many issues with unicode and lacks many functions.
See also:
 - #1428494: "Prefer linking against ncursesw over ncurses library" (so I consider this issue as a regression).
 - #4787
(reuse the nosy list from #7384)

Does anyone agree with me?

Just a short explanation: 
In #7384 I used the strict version of the patch for 2.7/3.2 because Thomas Dickey recommended not to load readline+ncurses and ncursesw
at the same time.
Actually the distros should either link readline against libtinfo
(Fedora) or only use ncursesw (DragonFly).
If someone feels confident that on Linux the linker can safely handle
conflicting global symbols in this situation, the patch for 2.6/3.1
could be used.

$ ldd $(/usr/bin/python3.1 -c 'import readline; print(readline.__file__)')|grep curses
 libncurses.so.5 => /lib/libncurses.so.5 (0xb7537000)
$ ldd /lib/libreadline.so.6|grep curses
 libncurses.so.5 => /lib/libncurses.so.5 (0xb76a6000)
> Actually the distros should either link readline 
> against libtinfo (Fedora) or only use ncursesw (DragonFly).
Ok, I should maybe open a *Debian* bug to ask to link readline to ncursesw (and another to ensure that Python3 is also liked to ncursesw).

There are two issues here:
(1) If libreadline is already linked against ncurses, there is no way that
 the readline module should be linked against ncursesw. This was the
 direct cause of the FreeBSD segfault, so this configuration is also
 prohibited in 2.6/3.1.
(2) Interaction between the readline and curses modules: 2.6/3.1 still
 allow readline+ncurses with curses+ncursesw. To be on the safe side,
 2.7/3.2 enforce all ncurses or all ncursesw.
(1) implies that if your readline module is linked against ncurses in 3.1,
you should find that libreadline is also linked against ncurses.

Hmm, I understood that your ldd lines implied that things don't work as
intended in 3.1, hence the explanation. Perhaps this wasn't the case. :)

For the record, I filed the following bug against Mageia's libreadline:
https://bugs.mageia.org/show_bug.cgi?id=2156 

> I should maybe open a *Debian* bug
Done:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602720
I don't think that we should drop support of libncurses because it is still the only option on some OSes. I'm closing the issue because it is now fixed in Debian which was my initial concern.