It would be useful to have a way to determine whether a socket is or is 
not already bound to a local port (i.e., has had "bind" or "connect" 
called on it).  It's tempting to call socket.socket.getsockname(), but 
the behavior of this method is essentially undefined (i.e., it's 
whatever the underlying platform feels like doing, and there seem to be 
no constraints on that -- Unix systems typically return what seems to be 
someone's idea of a null address, while Windows systems currently raise 
an exception.).  So an extension API is needed to probe this state.

Suggest adding a method "is_bound" which returns a boolean.

What happened to my issue metadata?

Given that the underlying platform has no support for that, it will be
difficult to implement correctly across all systems.

Indeed.  Calls for some design chops.  Again, it's a question of what
the socket.socket class really is.

Bill

On 8/30/07, Martin v. Löwis <report@bugs.python.org> wrote:
>
> Martin v. Löwis added the comment:
>
> Given that the underlying platform has no support for that, it will be
> difficult to implement correctly across all systems.
>
> ----------
> nosy: +loewis
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue1062>
> __________________________________
>

perhaps you can subclass socket.socket and make a function wrapper around bind and connect that sets a variable if called
like:
class sock(socket.socket):
    def bind(self,*args):
        self.is_bound = True

oops should be
class sock(socket.socket):
    _bind = socket.socket.bind
    def bind(self,*args):
        self.is_bound = True
        self._bind(self,*args)

The suggested subclass might have to call the default bind(("", 0)) before running certain other operations, including connect(), send[to](), recv[from](), since these operations are meant to automatically bind if necessary.