summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorJeremy Hylton <jeremy@alum.mit.edu>2001-12-14 16:15:11 (GMT)
committerJeremy Hylton <jeremy@alum.mit.edu>2001-12-14 16:15:11 (GMT)
commit2a05bc72d61377772ed988507bd67961bcbf35a0 (patch)
tree64302c77803d821592ba89cbb6ac16efcc91d48b /Doc
parent81feb6c201f0be1d08a40e5638d4dd215e0bbe6b (diff)
downloadcpython-2a05bc72d61377772ed988507bd67961bcbf35a0.zip
cpython-2a05bc72d61377772ed988507bd67961bcbf35a0.tar.gz
cpython-2a05bc72d61377772ed988507bd67961bcbf35a0.tar.bz2
Partial fix for problem in SF buf #487458
Rev 1.20 introduced a call to getpeername() in the dispatcher constructor. This only works for a connected socket. Apparently earlier versions of the code worked with un-connected sockets, e.g. a listening socket. It's not clear that the code is supposed to accept these sockets, because it sets self.connected = 1 when passed a socket. But it's also not clear that it should be a fatal error to pass a listening socket. The solution, for now, is to put a try/except around the getpeername() call and continue if it fails. The self.addr attribute is used primarily (only?) to produce a nice repr for the object, so it hardly matters. If there is a real error on a connected socket, it's likely that subsequent calls will fail too.
Diffstat (limited to 'Doc')
0 files changed, 0 insertions, 0 deletions