Raymond Hettinger added the comment:
My vote is for leaving this alone and letting the higher level
functions be more clever. Changing this function is certain to
break existing code in unpredictable ways.
That is sensible. Marking this as closed.
--
resolution: - wont fix
Steve Dower added the comment:
Automatically quoting arguments is more complicated than simply concatenating
quotes, unfortunately, and people are guaranteed to have come up with ways to
make it work already.
My vote is for leaving this alone and letting the higher level functions be
more
Mark Lawrence added the comment:
I believe the patch on #1576120 is related to this but it was never reviewed.
--
nosy: +BreamoreBoy
versions: +Python 3.4, Python 3.5 -Python 3.3
___
Python tracker rep...@bugs.python.org
Raymond Hettinger added the comment:
I believe the problem lies with the way that Windows implements
the 'exec' functions.
Yes, that is that cause of the observed behavior. See the first note in the
remarks section on the relevant MSDN entry at
Raymond Hettinger added the comment:
I believe the problem lies with the way that Windows implements
the 'exec' functions.
Yes, that is that cause of the observed behavior. See the first note in the
remarks section on the relevant MSDN entry at
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
Removed message: http://bugs.python.org/msg222989
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20451
___
Raymond Hettinger added the comment:
I no longer have a Windows box to test this but any proposed patch needs to
make sure it doesn't break code that is already manually escaping the inputs.
--
nosy: +loewis, steve.dower, tim.golden, tim.peters
___
Changes by Zachary Ware zachary.w...@gmail.com:
--
nosy: +zach.ware
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20451
___
___
Python-bugs-list
R. David Murray added the comment:
I believe the problem lies with the way that Windows implements the 'exec'
functions. Windows isn't posix, and sometimes its attempts to fake it go
rather badly. So, I'm not sure what the actual rules are, but whatever they
are there should at least be a
Florian Bruhin added the comment:
I can't test this right now, but I'd guess you also have to escape a inside
an argument (with \ presumably), and a \ with \\. Maybe more, no idea.
Actually the documentation doesn't say anything about me _having_ to escape
anything, so I'd assume I don't
Saimadhav Heblikar added the comment:
i have tried a workaround for this issue by explicitly escaping args so that
same result is produced on all platforms.this patch does NOT change the
behavior on non-NT platforms.
If this patch is accepted,i also recommend to specify on the help pages,that
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20451
___
___
New submission from Florian Bruhin:
The os.exec* functions seem to mangle arguments on Windows. So far I noticed
the supplied argv gets split on spaces, and double-quotes get stripped when not
escaped.
Example, on Windows 7:
platform.platform()
'Windows-7-6.1.7601-SP1'
os.execlp('python',
13 matches
Mail list logo