From: Mark Dickinson <dickinsm@gmail.com>
Date: Sat, 19 Jul 2014 20:45:06 +0000 (+0100)
Subject: Issue #22006: Remove outdated _thread caveat.  Thanks Dan O'Reilly for the report.
X-Git-Tag: v3.4.2rc1~205
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e004c6cad590c973faabb5e278eab2ae768b214f;p=python

Issue #22006: Remove outdated _thread caveat.  Thanks Dan O'Reilly for the report.
---

diff --git a/Doc/library/_thread.rst b/Doc/library/_thread.rst
index 2e130c1e52..a787e2fd4b 100644
--- a/Doc/library/_thread.rst
+++ b/Doc/library/_thread.rst
@@ -176,10 +176,6 @@ In addition to these methods, lock objects can also be used via the
 * Calling :func:`sys.exit` or raising the :exc:`SystemExit` exception is
   equivalent to calling :func:`_thread.exit`.
 
-* Not all built-in functions that may block waiting for I/O allow other threads
-  to run.  (The most popular ones (:func:`time.sleep`, :meth:`io.FileIO.read`,
-  :func:`select.select`) work as expected.)
-
 * It is not possible to interrupt the :meth:`acquire` method on a lock --- the
   :exc:`KeyboardInterrupt` exception will happen after the lock has been acquired.