Marko Rauhamaa wrote:
Nevertheless, the later socket object cannot unilaterally take over a socket using SO_REUSEADDR. The earlier socket object must have set the same option previously.
I just did an experiment that suggests that's not the case. I created a socket without SO_REUSEADDR, made a connection to it, and killed it. Then I created another socket within the timeout period with SO_REUSEADDR, and it succeeded. This was on MacOSX -- it's possible that other systems behave differently. -- Greg -- https://mail.python.org/mailman/listinfo/python-list
