This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients BreamoreBoy, martin.panter, niemeyer
Date 2015-10-07.02:20:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444184417.66.0.492376386382.issue17824@psf.upfronthosting.co.za>
In-reply-to
Content
The spawn() function has this code outside of any error handler:

pid, master_fd = fork()
if pid == CHILD:
    os.execlp(argv[0], *argv)

If fork() succeeds, there will actually be a parent Python process and a child Python process. If exec() then fails, an exception will escape the spawn() function in the child process, while the parent process will carry on as if all is well. Maybe it would be worthwhile studying how the “subprocess” module handles exec() failure in the child process.
History
Date User Action Args
2015-10-07 02:20:17martin.pantersetrecipients: + martin.panter, niemeyer, BreamoreBoy
2015-10-07 02:20:17martin.pantersetmessageid: <1444184417.66.0.492376386382.issue17824@psf.upfronthosting.co.za>
2015-10-07 02:20:17martin.panterlinkissue17824 messages
2015-10-07 02:20:17martin.pantercreate