From 754847f34b1f2cfc9683b143ca9e9e6ef054037f Mon Sep 17 00:00:00 2001 From: Christopher Larson Date: Fri, 3 Feb 2012 08:12:55 -0700 Subject: Revert the switch to futures for now Without it, we get random hangs on parse failure. With it, some folks have seen hangs even on successful cases. The former is clearly less problematic. This is temporary, until I can finish investigating the root causes of both issues. (Bitbake rev: db689a99beffea1a285cdfc74a58fe73f1666987) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie --- bitbake/lib/concurrent/futures/__init__.py | 18 ------------------ 1 file changed, 18 deletions(-) delete mode 100644 bitbake/lib/concurrent/futures/__init__.py (limited to 'bitbake/lib/concurrent/futures/__init__.py') diff --git a/bitbake/lib/concurrent/futures/__init__.py b/bitbake/lib/concurrent/futures/__init__.py deleted file mode 100644 index b5231f8aab..0000000000 --- a/bitbake/lib/concurrent/futures/__init__.py +++ /dev/null @@ -1,18 +0,0 @@ -# Copyright 2009 Brian Quinlan. All Rights Reserved. -# Licensed to PSF under a Contributor Agreement. - -"""Execute computations asynchronously using threads or processes.""" - -__author__ = 'Brian Quinlan (brian@sweetapp.com)' - -from concurrent.futures._base import (FIRST_COMPLETED, - FIRST_EXCEPTION, - ALL_COMPLETED, - CancelledError, - TimeoutError, - Future, - Executor, - wait, - as_completed) -from concurrent.futures.process import ProcessPoolExecutor -from concurrent.futures.thread import ThreadPoolExecutor -- cgit v1.2.3-54-g00ecf