From b1637bc9d66bbee3a036dae968ef05aa4d4ac15d Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Thu, 3 Jan 2013 18:23:42 -0800 Subject: portage._internal_caller: use global_event_loop It's more efficient to use global_event_loop than a local EventLoop instance, so do that when we know it's safe. --- pym/_emerge/PollScheduler.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'pym/_emerge') diff --git a/pym/_emerge/PollScheduler.py b/pym/_emerge/PollScheduler.py index 220394b41..b118ac157 100644 --- a/pym/_emerge/PollScheduler.py +++ b/pym/_emerge/PollScheduler.py @@ -1,4 +1,4 @@ -# Copyright 1999-2012 Gentoo Foundation +# Copyright 1999-2013 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 try: @@ -6,6 +6,7 @@ try: except ImportError: import dummy_threading as threading +import portage from portage.util._async.SchedulerInterface import SchedulerInterface from portage.util._eventloop.EventLoop import EventLoop from portage.util._eventloop.global_event_loop import global_event_loop @@ -35,7 +36,8 @@ class PollScheduler(object): elif main: self._event_loop = global_event_loop() else: - self._event_loop = EventLoop(main=False) + self._event_loop = (portage._internal_caller and + global_event_loop() or EventLoop(main=False)) self._sched_iface = SchedulerInterface(self._event_loop, is_background=self._is_background) -- cgit v1.2.3-1-g7c22