Message5286

Whenever I develop a server in Python, I want it to run on as many
platforms as possible with few special cases as possible.

Making a choice such as this means you have to alienate one community or
another.  In this case, it's the community of developers who are porting
apps from Java to Jython versus the community of developers who are
trying to get their cPython apps to work on Jython.  This becomes the
question of "who is our target audience?"  I fall in the latter category
and hence strongly recommend that the behavior should match that of
every other Python implementation (regardless of underlying platform).

Principle versus practicality;  Newcomers or Established community.  It
depends on the goal of the project.

If you decide to maintain the Java-esque behavior, this should be a
documentation bug then.  Some Jython users are cPython users at the core
and don't understand the underlying Java platform behavior (myself
included).  There should be big flashy lights on a page about sockets in
the Jython documentation that explains the discrepancy between cPython
server socket behavior and Jython server socket behavior.  This is a
darn good idea for Python server implementers who want their servers to
run under Jython.  They need to know that they need to do something
specifically different to get the behavior they are expecting.