Patch #1009075, bug #952953: allow execve with empty 2nd argument

This commit is contained in:
Armin Rigo 2004-09-27 19:54:33 +00:00
parent 9f90439817
commit b6aa856f25
2 changed files with 2 additions and 14 deletions

View file

@ -1226,8 +1226,8 @@ the individual parameters simply become additional parameters to the
\function{execl*()} functions. The \character{v} variants are good \function{execl*()} functions. The \character{v} variants are good
when the number of parameters is variable, with the arguments being when the number of parameters is variable, with the arguments being
passed in a list or tuple as the \var{args} parameter. In either passed in a list or tuple as the \var{args} parameter. In either
case, the arguments to the child process must start with the name of case, the arguments to the child process should start with the name of
the command being run. the command being run, but this is not enforced.
The variants which include a \character{p} near the end The variants which include a \character{p} near the end
(\function{execlp()}, \function{execlpe()}, \function{execvp()}, (\function{execlp()}, \function{execlpe()}, \function{execvp()},

View file

@ -2171,12 +2171,6 @@ posix_execv(PyObject *self, PyObject *args)
return NULL; return NULL;
} }
if (argc == 0) {
PyErr_SetString(PyExc_ValueError, "execv() arg 2 must not be empty");
PyMem_Free(path);
return NULL;
}
argvlist = PyMem_NEW(char *, argc+1); argvlist = PyMem_NEW(char *, argc+1);
if (argvlist == NULL) { if (argvlist == NULL) {
PyMem_Free(path); PyMem_Free(path);
@ -2253,12 +2247,6 @@ posix_execve(PyObject *self, PyObject *args)
goto fail_0; goto fail_0;
} }
if (argc == 0) {
PyErr_SetString(PyExc_ValueError,
"execve() arg 2 must not be empty");
goto fail_0;
}
argvlist = PyMem_NEW(char *, argc+1); argvlist = PyMem_NEW(char *, argc+1);
if (argvlist == NULL) { if (argvlist == NULL) {
PyErr_NoMemory(); PyErr_NoMemory();