Message5271

Having thought about this, my response is that the current behaviour
should remain, and that this bug should be closed as "won't fix".

Reasons include

1. All python socket module implementations defer to platform-specific
behaviour. I see no reason why jython should differ in this regard; it
should reflect the semantics of the underlying java platform, and not
inherit socket options if the underlying platform does not.

2. Doing this would force us to permit the setting of client socket
options on server sockets that are not valid for those server sockets.
This will lead to confusion among the users.

3. It is a simple exercise for the programmer to set whatever pending
options they wish on newly accept'ed client sockets.

However, rather than dismissing this RFE immediately, I will leave it
open for people to record dissenting opinions.