This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients BreamoreBoy, barry, brett.cannon, christopher.hogan, dstufft, eric.araujo, jaraco, mgiuca, ncoghlan, r.david.murray, steve.dower, tarek, zach.ware
Date 2015-08-20.17:42:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440092537.28.0.231160815503.issue8987@psf.upfronthosting.co.za>
In-reply-to
Content
Well, it sounds like there may be no way around the fact that people may already be doing the extra needed quoting escaping internal quotes) and therefore that this change would break those use cases.  (I note that any such code must be conditional on windows vs unix, since escaping the quotes will break the same command executed on unix).  

Unless...what if we conditionalize it on whether or not '\"' and/or '\\' appears in the argument?

And yes, the fundamental problem is that Windows provides no way to call a program with a list of not-to-be-modified strings.  The problem with a .bat parsing its argument string differently from how everything else parses its argument string is not a new problem, and is faced by anyone using subprocess.  distutils is trying to be (relatively) platform agnostic, to my understanding, so again we'd have to actually parse the input, this time looking for '.bat' and quoting accordingly.

If we solve the .bat problem (as opposed to ignoring it like we currently do in subprocess) we should fix it in subprocess too.

This is certainly getting non-trivial :(
History
Date User Action Args
2015-08-20 17:42:17r.david.murraysetrecipients: + r.david.murray, barry, brett.cannon, jaraco, ncoghlan, tarek, eric.araujo, mgiuca, BreamoreBoy, zach.ware, steve.dower, dstufft, christopher.hogan
2015-08-20 17:42:17r.david.murraysetmessageid: <1440092537.28.0.231160815503.issue8987@psf.upfronthosting.co.za>
2015-08-20 17:42:17r.david.murraylinkissue8987 messages
2015-08-20 17:42:16r.david.murraycreate