Title: Document differences in SocketServer between Python 2.6 and 2.7
Type: Stage: resolved
Components: Documentation Versions: Python 2.7
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, gjb1002, martin.panter, pitrou, zach.ware
Priority: normal Keywords:

Created on 2012-03-26 20:53 by gjb1002, last changed 2020-04-27 04:03 by zach.ware. This issue is now closed.

Messages (4)
msg156869 - (view) Author: Geoffrey Bache (gjb1002) Date: 2012-03-26 20:53
Here I'm referring to the section about RequestHandler objects under the SocketServer page.
This appears to be the same in Python 2.6 and Python 2.7. But the objects don't behave the same, in two respects:

1) For finish() "If setup() or handle() raise an exception, this function will not be called." This is true in Python 2.6. It appears to no longer be true in Python 2.7, where finish() is called in a "finally" clause.

2) For handle(). "The default implementation does nothing". This is true up to a point, but using the default implementation has different effects. Specifically, if I try to read from a socket when the server has not written anything, I get an exception in Python 2.6 and an empty string in Python 2.7. Consider this code:


from SocketServer import TCPServer, StreamRequestHandler
import sys, socket
server = TCPServer((socket.gethostname(), 0), StreamRequestHandler)
host, port = server.socket.getsockname()
address = host + ":" + str(port)
print "Started server at", address



import sys, socket

servAddr = sys.argv[1]
host, port = servAddr.split(":")
serverAddress = (host, int(port))
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
sock.sendall("Some Message")
response = sock.makefile().read()
print "Got reply:", response

and compare the following:

$ python2.7 &
Started server at
$ python2.7
Got reply:
$ python2.6 &
Started server at
$ python
Traceback (most recent call last):
  File "", line 12, in <module>
    response = sock.makefile().read()
  File "/usr/lib/python2.7/", line 351, in read
    data = self._sock.recv(rbufsize)
socket.error: [Errno 104] Connection reset by peer

(doesn't matter which Python runs the client in the last case)

I am unsure whether this is a bug in Python 2.6, or really what the reasoning behind the behaviour difference is, but I think this change in behaviour is worth a small note in the documentation (how it will behave if you try to read when nothing has been written)
msg222243 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-07-04 00:01
@Geoffrey sorry about the delay in getting back to you.
msg330412 - (view) Author: Martin Panter (martin.panter) * (Python committer) Date: 2018-11-26 10:17
Regarding the first point, “finish” is no longer called after an exception. This was apparently changed in 2.7.4 (see Issue 14574), but Geoffrey was referring to older documentation.

Regarding the second point, about ECONNRESET vs graceful shutdown, this seems to be due to the “shutdown” call added to in “TCPServer.close_request” in Issue 6267.
msg367383 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2020-04-27 04:03
Since Python 2.7 is now at end-of-life, I'm closing the issue.
Date User Action Args
2020-04-27 04:03:34zach.waresetstatus: open -> closed

nosy: + zach.ware
messages: + msg367383

resolution: out of date
stage: needs patch -> resolved
2018-11-26 12:01:11BreamoreBoysetnosy: - BreamoreBoy
2018-11-26 10:17:48martin.pantersetnosy: + martin.panter
messages: + msg330412
2014-07-04 00:01:52BreamoreBoysetnosy: + BreamoreBoy, pitrou
messages: + msg222243
2012-03-28 04:55:29eric.araujosetstage: needs patch
versions: - Python 2.6
2012-03-26 20:53:45gjb1002create