Charles-François Natali added the comment:
I'm with Antoine, this is *really* going too far.
SOCK_CLOEXEC and friends are useful to avoid race conditions: there's
no such concern with the non-blocking flag.
Shaving one or two syscalls is IMO completely useless, and doesn't
justify the extra code
Guido van Rossum added the comment:
OK, let's forget about it.
--
resolution: - wont fix
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19813
STINNER Victor added the comment:
I don't see what I can do against a -10 vote! :-)
I opened the issue #19827 for the simple syscall optimization.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19813
New submission from STINNER Victor:
Since Linux 2.6.28, socket() syscall accepts a new SOCK_NONBLOCK flag in the
socket type. It avoids 1 or 2 extra syscalls to set the socket in non-blocking
mode. This flag comes also slowly in other operating systems: NetBSD, FreeBSD,
etc.
FreeBSD:
STINNER Victor added the comment:
Note: Python supports socket.SOCK_NONBLOCK since Python 3.2 (issue #7523).
--
nosy: +neologix
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19813
___
Antoine Pitrou added the comment:
This really sounds pointless to me. How many sockets do you create per second?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19813
___
