Added notes about the eventual disappearance of two-parameter bind(),

freddrake · freddrake · commit 7d68690d8d8a · 2000-04-04T17:48:30.000Z
connect(), and connect_ex().

I didn't make these deprecation notices since it was never a
documented feature.
diff --git a/Doc/lib/libsocket.tex b/Doc/lib/libsocket.tex
@@ -247,7 +247,11 @@ \subsection{Socket Objects \label{socket-objects}}
 
 \begin{methoddesc}[socket]{bind}{address}
 Bind the socket to \var{address}.  The socket must not already be bound.
-(The format of \var{address} depends on the address family --- see above.)
+(The format of \var{address} depends on the address family --- see
+above.)  \strong{Note:}  This method has historically accepted a pair
+of parameters for \constant{AF_INET} addresses instead of only a
+tuple.  This was never intentional and will no longer be available in
+Python 1.7.
 \end{methoddesc}
 
 \begin{methoddesc}[socket]{close}{}
@@ -259,7 +263,10 @@ \subsection{Socket Objects \label{socket-objects}}
 \begin{methoddesc}[socket]{connect}{address}
 Connect to a remote socket at \var{address}.
 (The format of \var{address} depends on the address family --- see
-above.)
+above.)  \strong{Note:}  This method has historically accepted a pair
+of parameters for \constant{AF_INET} addresses instead of only a
+tuple.  This was never intentional and will no longer be available in
+Python 1.7.
 \end{methoddesc}
 
 \begin{methoddesc}[socket]{connect_ex}{address}
@@ -269,6 +276,10 @@ \subsection{Socket Objects \label{socket-objects}}
 can still raise exceptions).  The error indicator is \code{0} if the
 operation succeeded, otherwise the value of the \cdata{errno}
 variable.  This is useful, e.g., for asynchronous connects.
+\strong{Note:}  This method has historically accepted a pair of
+parameters for \constant{AF_INET} addresses instead of only a tuple.
+This was never intentional and will no longer be available in Python
+1.7.
 \end{methoddesc}
 
 \begin{methoddesc}[socket]{fileno}{}
