Author terry.reedy
Recipients Jovik, docs@python, eric.smith, r.david.murray, terry.reedy
Date 2014-03-15.01:40:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394847624.98.0.663645464644.issue20927@psf.upfronthosting.co.za>
In-reply-to
Content
I am sure that using / instead of \, which is to say, not using os.sep, is the problem as / is *not* allowed in Windows command names even though the substitution works for paths given as options. In a Windows console,
> python # works
> .\python # works
> ./python # see /python as an option for the . program, which does not exist.

I suspect that shell=True cause subprocess to execute "shell ./app" (howver 'shell' is spelled on the system), with whatever other options and quotation are needed to make ./app work as an option passed to shell instead of a command to be executed directly.

I also suspect that passing ".\\app" might work, which would mean that you should use .%sapp" % os.sep to get a cross-platform string. If so, please close this issue.
History
Date User Action Args
2014-03-15 01:40:25terry.reedysetrecipients: + terry.reedy, eric.smith, r.david.murray, docs@python, Jovik
2014-03-15 01:40:24terry.reedysetmessageid: <1394847624.98.0.663645464644.issue20927@psf.upfronthosting.co.za>
2014-03-15 01:40:24terry.reedylinkissue20927 messages
2014-03-15 01:40:24terry.reedycreate