I have a chance to play with Python about around Feb 2008 because we have a Python fan. He even wrote some scripts in Python even though we worked on Windows (use Cygwin). I need to modify his scripts to implement my cool Spec-To-Test inititives. There are 2 aspects I like about Python scripts: OOP and whitespace indentation.

And it was the 1st time I’ve seen a language using whitespace indentation as statement block; which means super readability and that mandatory coding standard is always enforced! I could read the guy’s code on the 1st time looking at Python even though I didn’t know Python at that time.

In addition, it was the 1st time I’ve seen an OOP in scripting language; which enabled me to do a lot more. I can see myself become a fan.

Instead of hard-coding your paths, you can put them in path.txt. Then using “for /f” to go thru each line in path.txt, parse each line and process it.

Why do we do this? it’s because of flexibility. Everyone can have a personalized set of directories he/she wants to compile since it takes too long to compile everything without messing with the script. You can update your script w/0 your path file and vice versa.

MS Visual Studio 2005/2008 command line build utility vcbuild.exe doesn’t show just error projects. Finding them manually is time-consuming so I wrote a script to filter out everything except error projects w/ number of errors. The result will be saved into summary log file.