summaryrefslogtreecommitdiff
path: root/Lib/socketserver.py
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-10-29 10:41:51 +0300
committerEzio Melotti <ezio.melotti@gmail.com>2011-10-29 10:41:51 +0300
commitf2b46973fe247fe0d8f431693b4f8409737935cd (patch)
tree889ac922c5d7649dad7adef374f5729289a332a5 /Lib/socketserver.py
parent8b46c3fd6454bee522e2a83a8852beb9b2f337f1 (diff)
downloadcpython-f2b46973fe247fe0d8f431693b4f8409737935cd.tar.gz
#13289: fix typo.
Diffstat (limited to 'Lib/socketserver.py')
-rw-r--r--Lib/socketserver.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/Lib/socketserver.py b/Lib/socketserver.py
index 73896081d1..0e2ba83d1d 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