From: Thomas Heller [mailto:thomas.heller@ion-tof.com]

I still have this code in one of my setup-scripts, the original version should be still in the archives, also some discussion about a test command:

I found the discussion. It looked good, but it seemed to peter out without consensus or any action. Can I suggest that *something* needs to be built in, even if it is minimal. Users can always override the default with something more complex, if they need to (or want to). My personal preference is to go with something like Greg Ward's suggestions, based on the Perl test harness. But there was never any code implemented to support this. Your version, if I understand it, simply imports each test module and runs its test() routine. I'm not too happy that the "OK/Not OK" reporting is left solely to the test routine - I'd rather there be a standard format. But maybe that's a job for a standard "test harness" module, rather than for the distutils command. Your version also seems to include code coverage reporting (which I *like*!!) but I can't find the code_coverage module in my distribution - is it a local module? But as I said, I'd rather see your version (with all my reservations) included and standard, than have nothing at all. Paul.