Re: [Pyunit-interest] Modifications to PyUnit

[Shae E. <sh...@ua...>]

Nathan Heagy wrote:

> The only other solution I can think of is reloading every module in
> sys.modules. The GUI could keep a list of which it was using, and reload all
> the others. As for chaining errors I think this could be solved by reloading
> the set of modules twice.

will that work if you have chains deeper than two? I don't think so. The
logic of it all isn't totally clear to me, so I may be wrong.

> Indeed. The disadvantage is that it is hard to make the results realtime. Most
> tests take only seconds to run. However a large project that has thousands of
> tests and takes minutes to run would not get any feedback from the cgi until
> all the tests have been run, even if the first failed. Of course there is the
> option of a server side push or even a reload/refresh, both of which I'm quite
> familiar with.

or possibly a tiny java applet that can read from a socket and a
javascript that updates a textarea? maybe that's too much overhead.

PS. I'll play with the Tkinter GUI when I have time, thanks for
releasing it.
-- 
sHae mAtijs eRisson (sH...@wE...) gEnius fOr hIre
   bRing mE fIve sQuirrels aNd nO oNe wIll gEt hUrt
13:00pm up 1 season, 1 squirrel, load average: 1+1j 0.5+2j 0.2+0.5j