From 72044f05a8efcc6c96cd5aa22d9062f75576df75 Mon Sep 17 00:00:00 2001 From: Brett Cannon Date: Wed, 21 Nov 2007 01:06:39 +0000 Subject: [PATCH] Fix an accidental re-typing of a word. --- pep-3116.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pep-3116.txt b/pep-3116.txt index 16324db6e..f7eb14115 100644 --- a/pep-3116.txt +++ b/pep-3116.txt @@ -429,7 +429,7 @@ Non-blocking I/O Non-blocking I/O is fully supported on the Raw I/O level only. If a raw object is in non-blocking mode and an operation would block, then ``.read()`` and ``.readinto()`` return ``None``, while ``.write()`` -returns 0. In order to put an object in object in non-blocking mode, +returns 0. In order to put an object in non-blocking mode, the user must extract the fileno and do it by hand. At the Buffered I/O and Text I/O layers, if a read or write fails due