Added notes about the eventual disappearance of two-parameter bind(),
connect(), and connect_ex(). I didn't make these deprecation notices since it was never a documented feature.
This commit is contained in:
parent
b49dc75f51
commit
7d68690d8d
|
@ -247,7 +247,11 @@ to the socket on the other end of the connection.
|
||||||
|
|
||||||
\begin{methoddesc}[socket]{bind}{address}
|
\begin{methoddesc}[socket]{bind}{address}
|
||||||
Bind the socket to \var{address}. The socket must not already be bound.
|
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}
|
\end{methoddesc}
|
||||||
|
|
||||||
\begin{methoddesc}[socket]{close}{}
|
\begin{methoddesc}[socket]{close}{}
|
||||||
|
@ -259,7 +263,10 @@ Sockets are automatically closed when they are garbage-collected.
|
||||||
\begin{methoddesc}[socket]{connect}{address}
|
\begin{methoddesc}[socket]{connect}{address}
|
||||||
Connect to a remote socket at \var{address}.
|
Connect to a remote socket at \var{address}.
|
||||||
(The format of \var{address} depends on the address family --- see
|
(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}
|
\end{methoddesc}
|
||||||
|
|
||||||
\begin{methoddesc}[socket]{connect_ex}{address}
|
\begin{methoddesc}[socket]{connect_ex}{address}
|
||||||
|
@ -269,6 +276,10 @@ instead of raising an exception for errors returned by the C-level
|
||||||
can still raise exceptions). The error indicator is \code{0} if the
|
can still raise exceptions). The error indicator is \code{0} if the
|
||||||
operation succeeded, otherwise the value of the \cdata{errno}
|
operation succeeded, otherwise the value of the \cdata{errno}
|
||||||
variable. This is useful, e.g., for asynchronous connects.
|
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}
|
\end{methoddesc}
|
||||||
|
|
||||||
\begin{methoddesc}[socket]{fileno}{}
|
\begin{methoddesc}[socket]{fileno}{}
|
||||||
|
|
Loading…
Reference in New Issue