Message10475

Calls to connect_ex on nonblocking sockets should report the sequence:

errno.EINPROGRES (if not immediately connected), errno.EALREADY (for subsequent calls until connected), E.ISCONN (once connected); or the corresponding error. Additionally, code written against the CPython behavior assumes that each poll takes some modest amount of time (this is what accounts for the original bug title, "Jython connect takes significantly longer than CPython socket connect"), or busy waiting loops will fail. Empirically this is about 1-2 milliseconds on my laptop. In the bug fix, I chose 1.25 milliseconds.

See http://www.gnu.org/software/libc/manual/html_node/Connecting.html for more details on connect_ex, which exposes the underlying connect behavior, especially for nonblocking connects.

Fixed as of https://hg.python.org/jython/rev/962002f7d96b