[Python-Dev] Heads up: socket.connect() breakage ahead

Gordon McMillan gmcm@hypernet.com
Fri, 24 Mar 2000 17:50:12 -0500

> Someone noticed that socket.connect() and a few related functions
> (connect_ex() and bind()) take either a single (host, port) tuple or
> two separate arguments, but that only the tuple is documented.
> Similar to append(), I'd like to close this gap, and I've made the
> necessary changes.  This will probably break lots of code.

This will indeed cause great wailing and gnashing of teeth. I've 
been criticized for using the tuple form in the Sockets 
HOWTO (in fact I foolishly changed it to demonstrate both 
> Similar to append(), I'd like people to fix their code rather than
> whine -- two-arg connect() has never been documented, although it's
> found in much code (even the socket module test code :-( ).
> Similar to append(), I may revert the change if it is shown to cause
> too much pain during beta testing...

I say give 'em something to whine about.

put-sand-in-the-vaseline-ly y'rs

- Gordon