From: Sam S. <sd...@gn...> - 2009-08-20 14:02:35
|
Bruno Haible wrote: > Paulo César Pereira de Andrade wrote: >> What I believe is the culprit is /usr/lib/python2.6/pty.py:fork(), >> a copy below for convenience: > > Yup. It creates a tty. What sense does this make, if the output is > analyzed by a program? What if you just remove or bypass that tty code? Given that clisp is called incorrectly here (using a tty), I am no longer sure that -disable-readline is worth having. All it would do is _hide_ a bug in another program (in this case, pexpect calling clisp with a tty). Can you really imagine a situation when -disable-readline is necessary? Sam |