Antoine Pitrou <[email protected]> added the comment:
There would need to be some tests.
Also, this last part of the patch looks strange:
@@ -3001,6 +3072,10 @@
PyErr_SetString(PyExc_ValueError,
"can't use invalid socket value");
return -1;
+#ifdef HAVE_ACCEPT4
+ /* These flags are not inherited after accept */
+ type &= ~(SOCK_NONBLOCK & SOCK_CLOEXEC);
+#endif /* HAVE_ACCEPT4 */
What is it meant for? And why does it come right after a "return" statement?
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue10115>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
