Stéphane Glondu added the comment: > What platform is this on?
I'm on Linux (Debian testing). > Looking quickly through posix.execve (which is what I think gets called), it > looks like it just calls C's execve(). Yes, but I'm talking about os.execvp, here. With the search in PATH. > Also, what's your use case for this? I discovered that by accident while investigating another bug... > I realize it might be a standard behavior, but it seems like a bad idea to me. What is the bad idea? Keep looking in subsequent directories in PATH when you find a candidate for which execve() fails? Sorry, but I beg to differ, and POSIX is on my side. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19948> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
