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 pitrou
Recipients alex, christian.heimes, dstufft, janssen, matrixise, pitrou, zielmicha
Date 2017-09-05.22:49:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1504651769.34.0.06827895577.issue18880@psf.upfronthosting.co.za>
In-reply-to
Content
This will needlessly break code which until now accepts both kinds of sockets.

By the way, socket.shutdown() doesn't specify that *only* one direction is shut down when using SHUT_RD or SHUT_WR; what is guaranteed is that *at least* the given direction will shut down.  But there may be socket types where unidirectional shutdown is not supported and both directions will be shut down.  This is (approximately) what SSLSocket does -- though the SSL unwrapping part is a bit unintuitive as well.
History
Date User Action Args
2017-09-05 22:49:29pitrousetrecipients: + pitrou, janssen, christian.heimes, alex, dstufft, matrixise, zielmicha
2017-09-05 22:49:29pitrousetmessageid: <1504651769.34.0.06827895577.issue18880@psf.upfronthosting.co.za>
2017-09-05 22:49:29pitroulinkissue18880 messages
2017-09-05 22:49:29pitroucreate