From 59d5404bc79beaa39c76fb26012238b26e9b0166 Mon Sep 17 00:00:00 2001
From: Richard Oudkerk <shibturn@gmail.com>
Date: Thu, 10 May 2012 16:11:12 +0100
Subject: Issue #14753: Make multiprocessing treat negative timeouts as it did
 in 3.2

In Python 3.2 and earlier, Process.join() and Connection.poll()
treated negative timeouts as zero timeouts.  Earlier versions from
the 3.3 line of development treat them as infinite timeouts.

The patch reverts to the old behaviour.
---
 Lib/multiprocessing/util.py | 15 ---------------
 1 file changed, 15 deletions(-)

(limited to 'Lib/multiprocessing/util.py')

diff --git a/Lib/multiprocessing/util.py b/Lib/multiprocessing/util.py
index da99063e57..9b6dac2006 100644
--- a/Lib/multiprocessing/util.py
+++ b/Lib/multiprocessing/util.py
@@ -295,18 +295,3 @@ class ForkAwareLocal(threading.local):
         register_after_fork(self, lambda obj : obj.__dict__.clear())
     def __reduce__(self):
         return type(self), ()
-
-
-#
-# Automatic retry after EINTR
-#
-
-def _eintr_retry(func):
-    @functools.wraps(func)
-    def wrapped(*args, **kwargs):
-        while True:
-            try:
-                return func(*args, **kwargs)
-            except InterruptedError:
-                continue
-    return wrapped
-- 
cgit v1.2.1