Re: [Pyunit-interest] PyUnitTestBrowser

[Phlip <ppl...@om...>]

Steve Purcell sez:

> Was very interested to see PUB. As a Brit, I have a strong affinity for
> things with that name. Many Python folk don't have the Python Mega Widgets
> installed, so you might also consider a less fancy GUI front-end in the
> interest of making it run 'out of the box' for all Python users. Same
> goes for the 'mock' module, which presumably isn't required to run
> the GUI.
>
> Great idea.

Thanks!

If I specialized a second browser, Pmw-free, it would need scrolled canvases 
and scrolled list boxes. Having never done Python UIs without Pmw I'm 
unfamiliar with how totally much this would suck. So I'd have to roll my own.

And forget the splitter bar (did you notice it? ;)

Instead of specializing, I think I'l detect Pmw on the fly and if it's not 
there call into an adapter layer that reinvents it. This means when the Great 
Washed Masses upgrade to Pmw the splitter bar will reappear and everything 
else will stay the same.

I need to try to defend Pmw because TreeBox uses it, and that (most 
excellent) widget is worth half the price of admission.

> Anyway, as far as reloading modules is concerned, you might want to check
> out something I wrote on the topic when I solved the problem for the
> original PyUnit GUI test runner:
>
>   http://pyunit.sourceforge.net/notes/reloading.html

I'l plug into this soon.

I was going to leave this thread here despite I discovered the short-term 
fix. I was test-firsting the bundled Debug.py, and Browser.py imports it. So 
(per your circular usage bugs), I kept testing the naturally used version, 
not the reloaded one. So when I test-firsted something else and everything 
worked I said duh! but wasn't going to reply to my own post here. ;-)

-- 
  Phlip
   http://www.greencheese.org/PhilosophyBrethrenThree
  --  "In my experience, the customer doesn't know what he wants
       until you don't give it to him." --David Brady  --