[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module
Vetoshkin Nikita
report at bugs.python.org
Tue Oct 12 22:49:14 CEST 2010
Vetoshkin Nikita <nikita.vetoshkin at gmail.com> added the comment:
Thanks! I can see the problem now, but I think checking should be done like this:
>>> fcntl.fcntl(c, fcntl.F_GETFD) & fcntl.FD_CLOEXEC
0
>>> fcntl.fcntl(s, fcntl.F_GETFD) & fcntl.FD_CLOEXEC
1
and with accept4() call I've got flag set:
>>> fcntl.fcntl(c, fcntl.F_GETFD) & fcntl.FD_CLOEXEC
1
>>> fcntl.fcntl(s, fcntl.F_GETFD) & fcntl.FD_CLOEXEC
1
Don't know how to properly check if accept4 is available.
Second attempt - dropping flags from sock_type should be done on Python level in socket.py and I don't quite like idea to check if SOCK_CLOEXEC is in locals every time.
----------
Added file: http://bugs.python.org/file19206/issue7523_py3k_accept4.diff
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7523>
_______________________________________
More information about the Python-bugs-list
mailing list