summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-10-29 10:40:20 +0300
committerEzio Melotti <ezio.melotti@gmail.com>2011-10-29 10:40:20 +0300
commitef4e2fa1714cbc9d0dfda648769ba5c98235ec4d (patch)
treee75f77c8461780022dbb0e2d6bc3b74cae8b158b
parent67d5d0ed442e24cc4ae4ccb1264451844ac88a0c (diff)
downloadcpython-git-ef4e2fa1714cbc9d0dfda648769ba5c98235ec4d.tar.gz
#13289: fix typo.
-rw-r--r--Lib/SocketServer.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/SocketServer.py b/Lib/SocketServer.py
index f1fd78b86b..71b9caa973 100644
--- a/Lib/SocketServer.py
+++ b/Lib/SocketServer.py
@@ -82,7 +82,7 @@ On the other hand, if you are building e.g. an HTTP server, where all
data is stored externally (e.g. in the file system), a synchronous
class will essentially render the service "deaf" while one request is
being handled -- which may be for a very long time if a client is slow
-to reqd all the data it has requested. Here a threading or forking
+to read all the data it has requested. Here a threading or forking
server is appropriate.
In some cases, it may be appropriate to process part of a request