Biggest problems I could see are in two areas, misinterpretation and structural. Depending on the filesystem, and current hardware setup, some of the files may still be being written to disk(say a network drive or during lots of other writes) when the tests are run. In terms of misinterepretation, you'd have to make it clear that it is in its test phase, and that installation finished without a hitch. Those are all I can see happening.
And as to the test's you asked me to run... I realize now I was supposed to use the svn trunk of pygame, not the 1.8 release. Redoing it all over right now, but with the problems fixed, I don't forsee any issues. :)
-TylerOn Wed, Apr 22, 2009 at 9:42 PM, René Dudfield <renesd@xxxxxxxxx> wrote:
That reminds me...
should we make the tests run at the end of an install automatically?
Should make it easier for people to figure out if there are problems... but might cause it's own problems too.
On Thu, Apr 23, 2009 at 2:39 PM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:One last step, run the unit test suite. I will only take a few minutes (still under construction).
python -c "import pygame.tests.go"
Tyler Laing wrote:
And that works! Fantastic, thank you gentlemen for all the assistance. Much appreciated.
-Tyler