➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nicdumz
Recipients docs@python, georg.brandl, kiilerix, neologix, nicdumz, pitrou
Date 2012-01-12.21:16:21
SpamBayes Score 2.2867592e-09
Marked as misclassified No
Message-id <1326402982.11.0.0757175288221.issue6774@psf.upfronthosting.co.za>
In-reply-to
Content 
> It's the other end which decides to return ENOTCONN upon shutdown(SHUT_RD) on OS X, which is questionable
> (not sure it's against the BSD socket API, since shutdown(SHUT_RD) doesn't have any counterpart in the TCP layer).

Exactly. The same code raises a socket.error in one platform (mac os) and not on another (linux). Why not document this questionable behavior?

I'm sorry, I realize that my original patch was imprecise. I'm not an expert here, and I simply read http://svn.python.org/view/python/trunk/Lib/test/test_socket.py?r1=64125&r2=68611&pathrev=68611 . Ok, fine -- it doesn't close the other end per se, but shutdown(SH_RD) after a FIN on MacOS raises a socket.error . This is questionable, unexpected, and should be documented.


If possible, I'd like to push for a rewording instead of a revert.
History
Date User Action Args
2012-01-12 21:16:22nicdumzsetrecipients: + nicdumz, georg.brandl, pitrou, kiilerix, neologix, docs@python
2012-01-12 21:16:22nicdumzsetmessageid: <1326402982.11.0.0757175288221.issue6774@psf.upfronthosting.co.za>
2012-01-12 21:16:21nicdumzlinkissue6774 messages
2012-01-12 21:16:21nicdumzcreate