Building Python 2.2 - curses module test failure
Michael Hudson
mwh at python.net
Fri Feb 1 05:30:51 EST 2002
Nick Chalk <nick at leviathan.uklinux.net> writes:
> [ Apologies if this screws up the threading. My
> news server machine chose last night to have a
> crisis, and all of comp.lang.python ended up in
> lost+found. :-/ ]
>
> I pulled the three updated files from CVS, and
> rebuilt with the same debugging, no optimization
> CFLAGS as before. The curses tests now run fine -
> no segfaults, no warnings of invalid pointers.
Good.
> One operator trap to watch for when running the
> tests - don't try to redirect stdout, ncurses
> doesn't like it. Unfortunately, if you do
> something like...
>
> make test 2>&1 | tee Test.log
>
> ...which is what I habitually do, ncurses doesn't
> warn you - it just fails hard. :-(
I can believe that. But if you run it exactly like that, test_curses
shoudln't run...
> Problem solved! Thanks for your help.
No problem. Thanks for the report!
Cheers,
M.
--
40. There are two ways to write error-free programs; only the third
one works.
-- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html
More information about the Python-list
mailing list