Missing pyWin32, Mark Harmond's windows library for python. I suppose
the installer could check for this and report the missing dependency.  I
have done this myself with DotNet dlls, and some installers give you a
chance to write a routine to check complex missing dependencies. 
Although the easiest way I can think of is wrap an import statement with
a try catch and report either success or failure.  

workaround, before you install roundup, make sure you have install
pywin32 from Mark Hammond's web site.

Luis,
thanks for creating this issue!

I wonder if we could just include the pyWin32 library in the installer?

I don't know.  I guess I would make a distinction between needing pywin
for the installer and needing it for roundup.

If the installer needs it then yes it could be included, but I think
that roundup needs it.  The problem is that there is a different pywin32
library for every version of python (2.5,2.6,2.7,...) so it is easier
just to throw an error and ask the user to figure out which version he
needs to install for his python setup.

Ah, you are right of course, that we cannot know the python binary unless we 
also include python itself. ;)

I wonder what roundup would use pywin, though.