Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - duplicate
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19066
___
anatoly techtonik added the comment:
I tested with 2.7 and 3.3, but this is true for any version.
If the bug is actual for Python 2.6, 3.1 and 3.2 why should I uncheck them?
Versions field description doesn't say that I should mark only latest change.
In addition, people (unlikely, but still)
Terry J. Reedy added the comment:
The versions are the versions that will be patched for the issue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19066
___
anatoly techtonik added the comment:
It should be documented somehow then. At least in the field tooltip.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19066
___
Richard Oudkerk added the comment:
See
http://bugs.python.org/issue436259
This is a problem with Window's implementation of spawn*() and exec*(). Just
use subprocess instead which gets this stuff right.
Note that on Windows exec*() is useless: it just starts a subprocess and exits
the
anatoly techtonik added the comment:
On Sun, Sep 29, 2013 at 2:05 PM, Richard Oudkerk rep...@bugs.python.org wrote:
See http://bugs.python.org/issue436259
I am not sure that I should see there. There is discussion of DOS,
which is not supported, also some complain about Windows execv
Richard Oudkerk added the comment:
I am not sure that I should see there. There is discussion of DOS,
which is not supported, also some complain about Windows execv
function, which deprecated since VC++ 2005 (which I hope also not
supported). Can you be more specific?
_spawn*() and _exec*()
anatoly techtonik added the comment:
On Sun, Sep 29, 2013 at 3:03 PM, Richard Oudkerk rep...@bugs.python.org wrote:
_spawn*() and _exec*() are implemented by the C runtime library. spawn*()
and execv() are (deprecated) aliases.
It is said that execv() is deprecated, but it is not said that
Richard Oudkerk added the comment:
It is said that execv() is deprecated, but it is not said that it is
alias of _execv(). It is only said that _execv() is C++ compliant.
http://msdn.microsoft.com/en-us/library/ms235416(v=vs.90).aspx
Microsoft seems to have decided that all functions in the
anatoly techtonik added the comment:
Hey. This ticket is about os.execv failing on spaced paths on Windows. It is
not a duplicate of issue19124.
--
resolution: duplicate -
status: closed - open
___
Python tracker rep...@bugs.python.org
anatoly techtonik added the comment:
On Sun, Sep 29, 2013 at 8:48 PM, Richard Oudkerk rep...@bugs.python.org wrote:
Don't we have such function already? I don't see the problem in
quoting the string.
No one seems to know how to write such a quoting function.
Why escape quotes with slash
Richard Oudkerk added the comment:
Hey. This ticket is about os.execv failing on spaced paths on Windows. It
is not a duplicate of issue19124.
It is a duplicate of #436259 [Windows] exec*/spawn* problem with spaces in
args.
--
___
Python tracker
Changes by Richard Oudkerk shibt...@gmail.com:
--
nosy: -sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19066
___
___
Python-bugs-list mailing
Terry J. Reedy added the comment:
Reminder: you are not supposed to re-open issues.
I agree with Richard that this is a duplicate as submitted. The difference is
that we now have subprocess; that is our fix for several problems. I will
re-close unless you make a *specific* suggestion for a
Terry J. Reedy added the comment:
Please stop marking all versions. Use cntl-left click to select the appropriate
ones (currently at most 2.7, 3.3, 3.4 for users). Which version did you run
your file with?
--
nosy: +loewis, terry.reedy
stage: - test needed
type: - behavior
versions:
New submission from anatoly techtonik:
If file to be executed with os.execv on Windows is located in directory with
spaces, Python fails. This doesn't fail on Linux. To test, run:
testexecv.py spaced
testexecv.py is attached.
--
components: Library (Lib), Windows
files:
16 matches
Mail list logo