"Eric S. Raymond" <esr@thyrsus.com> writes:
Andrew Kuchling <akuchlin@mems-exchange.org>:
* Drop cursesmodule and package it separately. (Any other obsolete modules that should go?)
Annoyingly enough, I may need this to stay in, for use by the new Linux-kernel configuration system I'm writing. Why is it on the hit list?
IIRC, it's because nobody really maintains it, and those that care about it, use a different one (either ncurses module, or a newer cursesmodule). So from what i understand, you get complaints, but no real advantage to having it there. I'm just trying to summarize, not fall on either side (some people get touchy about issues like this). --Dan
Daniel Berlin+list.python-dev <dan@cgsoftware.com>:
Andrew Kuchling <akuchlin@mems-exchange.org>:
* Drop cursesmodule and package it separately. (Any other obsolete modules that should go?)
Annoyingly enough, I may need this to stay in, for use by the new Linux-kernel configuration system I'm writing. Why is it on the hit list?
IIRC, it's because nobody really maintains it, and those that care about it, use a different one (either ncurses module, or a newer cursesmodule). So from what i understand, you get complaints, but no real advantage to having it there.
OK. Then what I guess I'd like is for a maintained equivalent of this to join the core -- the ncurses module you referred to, for choice. I'm not being random. I'm trying to replace the mess that currently constitutes the kbuild system -- but I'll need to support an equivalent of menuconfig. -- <a href="http://www.tuxedo.org/~esr">Eric S. Raymond</a> "The state calls its own violence `law', but that of the individual `crime'" -- Max Stirner
Eric S. Raymond writes:
OK. Then what I guess I'd like is for a maintained equivalent of this to join the core -- the ncurses module you referred to, for choice.
See the "Whither cursesmodule" thread in the python-dev archives: http://www.python.org/pipermail/python-dev/2000-February/003796.html One possibility was to blow off backward compatibility; are there any systems that only have BSD curses, not SysV curses / ncurses? Given that Pavel Curtis announced he was dropping BSD curses maintainance some years ago, I expect even the *BSDs use ncurses these days. However, Oliver Andrich doesn't seem interested in maintaining his ncurses module, and someone just started a SWIG-generated interface (http://pyncurses.sourceforge.net), so it's not obvious which one you'd use. (I *would* be willing to take over maintaining Andrich's code; maintaining the BSD curses version just seems pointless these days.) --amk
Andrew Kuchling <akuchlin@mems-exchange.org>:
Eric S. Raymond writes:
OK. Then what I guess I'd like is for a maintained equivalent of this to join the core -- the ncurses module you referred to, for choice.
See the "Whither cursesmodule" thread in the python-dev archives: http://www.python.org/pipermail/python-dev/2000-February/003796.html
One possibility was to blow off backward compatibility; are there any systems that only have BSD curses, not SysV curses / ncurses? Given that Pavel Curtis announced he was dropping BSD curses maintainance some years ago, I expect even the *BSDs use ncurses these days.
BSD curses was officially declared dead by its maintainer, Keith Bostic, in early 1995. Keith and I conspired to kill it of in favor of ncurses :-). -- <a href="http://www.tuxedo.org/~esr">Eric S. Raymond</a> If gun laws in fact worked, the sponsors of this type of legislation should have no difficulty drawing upon long lists of examples of criminal acts reduced by such legislation. That they cannot do so after a century and a half of trying -- that they must sweep under the rug the southern attempts at gun control in the 1870-1910 period, the northeastern attempts in the 1920-1939 period, the attempts at both Federal and State levels in 1965-1976 -- establishes the repeated, complete and inevitable failure of gun laws to control serious crime. -- Senator Orrin Hatch, in a 1982 Senate Report
participants (3)
-
Andrew Kuchling -
dan＠cgsoftware.com -
Eric S. Raymond