why don't many test frameworks support file-output?

[kanchy kang]

one question for you:
have anyone teach you how to listen to other's idea before?

this mail-list is only for exchanging idea, and aslo i provided my 
suggestion or "practice" or idea for test framework. if what i said is 
wrong, you can point it out as you like.
did i order anybody, or you?

you are the man not likely to listening to others.
if i would hire some, i don't think you are.
if you are some software's author, i would not use the software.
just because you are the man not likely to listening to others.

hehe


>From: Scott David Daniels <scott.daniels at acm.org>
>To: python-list at python.org
>Subject: Re: why don't many test frameworks support file-output?
>Date: Fri, 24 Feb 2006 07:43:20 -0800
>
>kanchy kang wrote:
> >
> > I don't think redirecting stdout to a file is a good resolution.
>Nobody is suggesting:
>      python program.py >output
>or
>      program.py >output
>
>What is being suggested is:
>      import sys
>      import module
>      original, sys.stdout = sys.stdout, open('output', 'w')
>      try:
>          module.main()
>      finally:
>          result, sys.stdout = sys.stdout, original
>          size = result.tell()
>          result.close()
>          print size, 'bytes written to file "output"'
>
>If, however, you want everyone else to conform to your personal idea
>of "best practices," then hire them and tell them to do it your way.
>
>--Scott David Daniels
>scott.daniels at acm.org
>--
>http://mail.python.org/mailman/listinfo/python-list

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/