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 skrah
Recipients Arfrever, akuchling, asmodai, mark.dickinson, r.david.murray, rpetrov, skrah, vstinner
Date 2010-10-24.11:10:31
SpamBayes Score 0.027382854
Marked as misclassified No
Message-id <1287918633.02.0.471002345837.issue9408@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2010-10-24 11:10:33skrahsetrecipients: + skrah, akuchling, mark.dickinson, vstinner, asmodai, rpetrov, Arfrever, r.david.murray
2010-10-24 11:10:33skrahsetmessageid: <1287918633.02.0.471002345837.issue9408@psf.upfronthosting.co.za>
2010-10-24 11:10:31skrahlinkissue9408 messages
2010-10-24 11:10:31skrahcreate