Georg Brandl <[EMAIL PROTECTED]> writes:
>> Well, this still has the faint whiff of impossibility about it. Are
>> you sure it's setupterm() that's doing the damage? Can you reproduce
>> interactively?
>
> Yep.
> Alone, the setupterm call [curses.setupterm(sys.__stdout__.fileno())] does
> nothing remarkable, but when it is done inside of curses.initscr() /
> curses.endwin()
> the terminal is not restored properly.
Ah! That does indeed make some small amount of sense.
> If setupterm() is to be tested, I think it should be executed before
> initscr().
Sounds good. What are you waiting for? :)
Cheers,
mwh
--
<etrepum> Jokes around here tend to get followed by implementations.
-- from Twisted.Quotes
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
