Author nicdumz
Recipients georg.brandl, nicdumz
Date 2009-08-24.08:45:19
SpamBayes Score 7.33301e-05
Marked as misclassified No
Message-id <1251103521.34.0.917057608479.issue6774@psf.upfronthosting.co.za>
In-reply-to
Content
I had a bad time understanding what happens in Mac OS X after a shutdown
call: after calling shutdown(SH_WR) on side A, a corresponding
shutdown(SH_RD) on side B would raise a socket.error: socket is not
connected.
It is quite surprising when you are used to sockets in Linux, which
expect you to shut one end, and then the other one.

It turns out that under Mac OS X, a shutdown call closes the connection
on the other half. And the only mention I could find of this behavior
was here, r68611 :
http://svn.python.org/view/python/trunk/Lib/test/test_socket.py?r1=64125&r2=68611&pathrev=68611

I think that the documentation should specify that (surprising)
behavior: I attached a patch explaining that detail.


Thanks!
History
Date User Action Args
2009-08-24 08:45:21nicdumzsetrecipients: + nicdumz, georg.brandl
2009-08-24 08:45:21nicdumzsetmessageid: <1251103521.34.0.917057608479.issue6774@psf.upfronthosting.co.za>
2009-08-24 08:45:20nicdumzlinkissue6774 messages
2009-08-24 08:45:19nicdumzcreate