[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: bug regarding os.execute?
- From: "Robert Raschke" <rtrlists@...>
- Date: Mon, 21 Jul 2008 10:40:29 +0100
On 7/21/08, Thomas Lauer <email@example.com> wrote:
> Actually, this seems to be an artifact of CMD.EXE and not so much a rule
> in Windows. (Rules in Windows? Wonder what that means anyway;-)
> At least my command-line interpreter (the delectable JPSoft 4NT/Take
> Command) as well as the Start menu Run... box execute both commands
> above without problem. (Indeed, I'll take this opportunity to point
> interested readers to the freeware version of the JPSoft CLI (called
> TCC/LE) which beats CMD.EXE hands down in terms of features and
Well, it's actually system() that gets invoked by os.execute(). And
system() in turn goes and finds CMD.EXE to execute your command line.
And, yes, I hate Windows too. Took me two days to figure out the weird
quoting, for example.
I guess if you want to use some other command interpreter on Windows,
you'll need to write a wrapper function for that using _exec() et al.