Babak:

This is a lot of code!  Holy smokes.  Good hustle.  :)

There are some style and formatting issues that keep cropping up.  I've highlighted a bunch, but you'll really want to run each of these scripts through pep8 before submitting again.

Also, to make things easier on your reviewers - how about breaking up your review requests into the different platforms and architectures, as opposed to one big, monolithic review request?

Thanks!

-Mike

alphabetical order, and then two linebreaks between the imports and the from import.  Two linebreaks between the from imports and the first function, and two linebreaks between functions.

These comments apply to all files below.

How come only some of these have #! lines at the top?

You might benefit instead with different syntax for long strings - see http://docs.python.org/tutorial/introduction.html#strings

See other comment, re: long strings.

space after commas

Space after commas

Same, re: this directory existing...

Are we sure that "C:\Program Files (x86)" will exist?

Can we assume that this directory exists?

spaces before *

ws

Spaces on either side of the +

spaces on either side of the =

Spaces on either side of the =

Space before the *.

Spaces on either side of the =, +'s

Spaces between functions.  Applies to all below.

Spaces after commas, on either side of =

Typo - "installation" - also, why do some of these give off the "installation complete" message, and others do not?

Spaces (see above)

Spaces for =

ws

Still need this?

Hm - maybe we'll just use standard escaped quotes instead of those weird characters.

I see - we build the folder for them...gotcha.  Do we clean up afterwards?

ws

We should probably be consistent with our capitalization.

Shorten to <= 80 chars please, and space after commas

Please put these in alphabetical order

Two linebreaks between this from import and the other imports.

For these, spaces after the commas.  And the PossibleApplications line needs to be broken up over several lines.

Spaces on either side of the = sign

Spaces on either side of the =

Instead of running commands right from the root of the script, I think I'd prefer to have a main function that runs each command, and then to call that main function.

?

ws

Temp file

temp file

temp file

temp file

Spaces after commas

Spaces on either side of =

ws

ws

Needs formatting cleanup, spaces on either side of =...

This entire series of instructions, starting from line 26, should probably be in a "main" function, which gets called at the end of the file with sys.argv.

I'm seeing lots of "prints" everywhere...shouldn't we be piping to stdout and stderr?

ws

I think this tilde file is likely temporary, and shouldn't have been included in the review request.