Aren't unit tests fun in Python? I've been stuck doing a bunch of them lately, and I quite like the way that no extraneous code is left in the working modules themselves. Basic stuff, but it's nice to present a finished application in a nice bundle with a separate bunch of unit tests to be examined by anyone.

The problem I have is making sure I don't put too many tests into a single testing module. Best to keep things nice and manageable.

I also need to go through my code with PyChecker and remove any unwanted variables that snuck in through the back door. That module is incredibly useful for testing and cleaning a Python application. I used it a lot for cleaning SalStat (when I worked on it).

SalStat has become a bit of an orphan lately. Downloads are okay and stable (~400-500/month) but nobody wants to contribute any code to it. I guess that's why the project died, even though a lot of people found it even more useful than the top commercial apps in the field. I even applied for a UI job at SPSS but received no answer whatsoever. That was surprising given that I've a) commercial experience in the field; b) lots of academic experience in the field (and qualifications); and c) had actually done the analysis already (though not implemented in SalStat, I had talked about it a few years ago).

I'm very sure that few other people had the same fitness as I had because the interfaces to stats packages are *&%!#@?£ awful (with one or two very minor exceptions) and show little evidence of good HCI work on them - at most, the usual "I've done my HCI-101 and that's all that anyone needs" input from the programmers - usually old ideas warmed over and badly implemented.

SourceForge is very slow tonight - I wonder if they're doing admin work behind the scenes, or is there a run on FireFox 1.5? I got it from a mirror - really good work folks and congrats to anyone involved.