Author eryksun
Recipients BreamoreBoy, Eli_B, eryksun, pekka.klarck, steve.dower, tim.golden, zach.ware
Date 2020-03-18.11:19:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584530342.06.0.11798383198.issue17023@roundup.psfhosted.org>
In-reply-to
Content
Why are new versions getting added to an issue that was closed 5 years ago? 

That said, I'd like to clarify that this was not and is not a bug. It happens that the CMD shell strips quotes out, but that doesn't make it valid. PATH in Windows is delimited by semicolons, not spaces, so paths with spaces should never be quoted. In particular, WINAPI SearchPathW, which CreateProcessW calls, leaves quotes in the directory name when testing whether a file is in the directory.

Also, the conclusion that Linux doesn't suffer from this problem is incorrect. The shell command that was used actually strips the quotes out as part of command-line pre-processing, i.e. `PATH=$PATH:"test"` results in the same PATH value as `PATH=$PATH:test`. But it will fail to find "script.sh" if you escape the quotes to make the shell add them literally to PATH, e.g. `PATH=$PATH:\"test\"`.
History
Date User Action Args
2020-03-18 11:19:02eryksunsetrecipients: + eryksun, tim.golden, pekka.klarck, BreamoreBoy, Eli_B, zach.ware, steve.dower
2020-03-18 11:19:02eryksunsetmessageid: <1584530342.06.0.11798383198.issue17023@roundup.psfhosted.org>
2020-03-18 11:19:02eryksunlinkissue17023 messages
2020-03-18 11:19:01eryksuncreate