rxvt + python problem: script output buffered and interactive output missing

Manoj Plakal terabaap at yumpee.org
Thu Nov 29 01:36:08 CET 2001

Chris Liechti wrote:

> Manoj Plakal <plakal at yumpee.org> wrote in news:3C04A742.50700 at yumpee.org:
>>I'm encountering a strange problem when I run
>>Python scripts and the Python interpreter in
>>an rxvt window (with tcsh) on the latest Cygwin.
>>This is with Win98/BeOpen Python 2.0/Cygwin 1.3.5/rxvt-2.7.2.
>>The scripts print some messages to stdout but
>>these gets buffered and appear only when the
>>app exits (it runs for a while). If I add
>>calls to flush stdout, then the messages appear
>>as they are printed.
>>If I run the Python interpreter itself, I
>>get no output at all, the shell just hangs,
>>I get the hourglass icon and I can eventually
>>break out with Ctrl-C's.
> yes i have the same behaviour on my machine... python mistakenly
> thinks that it has to thake its input from stdin/pipe instead of running 
> interactive. python runs if you specify "-i" explicit.
> i guess that it has something to do with the terminal name that rxvt sets, 
> so that an app doesn't know that its a console window.

       Cool, thanks, that works. Only problem is that now
       I can't quit out of the shell using Ctrl-D or Ctrl-Z.
       And Ctrl-C doesn't seem to produce a KeyboardInterrupt.

       The stty settings in tcsh seem to be fine, Ctrl-C/D/Z work
       in the shell.


More information about the Python-list mailing list