Logged In: YES 
user_id=431773

What did I expect? Well, obviously I expected it to "just work", but I don't 
have much idea what's going on "under the hood" and have always been 
puzzled by the need in os.popen... to specify the executable twice. And I 
have even less idea what's going on under the hood on Windows!

I was trying to use it in my code to work around bug 1057048 which applies 
to Windows. I figured if an executable with a space in its path name 
wouldn't get through as part of the command string, it might get through 
when specified as a separate 
argument.

So...yes if possible I think it would be very good to document what happens 
if executable and 
shell=True are both specified at the same time. Especially since it may be 
radically different on Windows and unix.

It'd also be nice to say in the module header that list2cmdline is part of this 
module, i.e. "If args is a sequence, it will beconverted to a string using the 
list2cmdline method." could be changed to: "If args is a sequence, it will be 
converted to a string using list2cmdline (below). I had the impression it was 
a standard module and failed miserably finding any documentation about it. 
Probably seems silly, since you know where to look, but I bet I'll not be the 
only one.