From: Ross Lagerwall Date: Thu, 22 Dec 2011 07:07:30 +0000 (+0200) Subject: Issue #11006: Don't issue low level warning in subprocess when pipe2() fails. X-Git-Tag: v3.2.3rc1~251 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=031bf95d3212d246a44e8e3a23ff32023ab905e9;p=python Issue #11006: Don't issue low level warning in subprocess when pipe2() fails. --- diff --git a/Misc/NEWS b/Misc/NEWS index 9168a55be0..c36b0196d2 100644 --- a/Misc/NEWS +++ b/Misc/NEWS @@ -97,6 +97,8 @@ Core and Builtins Library ------- +- Issue #11006: Don't issue low level warning in subprocess when pipe2() fails. + - Issue #11829: Fix code execution holes in inspect.getattr_static for metaclasses with metaclasses. Patch by Andreas Stührk. diff --git a/Modules/_posixsubprocess.c b/Modules/_posixsubprocess.c index 11b24a031f..4e38bbe63f 100644 --- a/Modules/_posixsubprocess.c +++ b/Modules/_posixsubprocess.c @@ -437,12 +437,6 @@ subprocess_cloexec_pipe(PyObject *self, PyObject *noargs) Py_END_ALLOW_THREADS if (res != 0 && errno == ENOSYS) { - if (PyErr_WarnEx( - PyExc_RuntimeWarning, - "pipe2 set errno ENOSYS; falling " - "back to non-atomic pipe+fcntl.", 1) != 0) { - return NULL; - } { #endif /* We hold the GIL which offers some protection from other code calling