joep wrote: >* If shell=True is required, then the executable is a build-in shell >command, which does not contain spaces, and, therefore, has no >problems
This is only true when you are referring to directly executable files. However, Shell=True is also required when you want to "execute" a file by it's association. For example, if you want to execute a ".pyw" file directly (i.e., by using whichever python executable is associated with that extension), you need Shell=True. IMHO, the subprocess module should not have been included as-is in the Python library. It is counter-intuitive, buggy, ill-documented, and has needless limitations in functionality. Regards, Gertjan. -- Gertjan Klein <[EMAIL PROTECTED]> -- http://mail.python.org/mailman/listinfo/python-list
