cool, thanks for the explanation! On 02/09/2014, holger krekel <[email protected]> wrote: > Hi Anatoly, > > On Fri, Aug 22, 2014 at 15:03 +0200, Anatoly Bubenkov wrote: >> Hi >> >> anybody knows about the source of such message after test run: >> >> Unhandled exception in thread started by <bound method >> WorkerPool._perform_spawn of <execnet.gateway_base.WorkerPool object at >> 0xf8dbe10>> > > It's a notorious issue during interpreter shutdown and has haunted > execnet for a long time. Basically some thread is still operating > while the interpreter objects (like sys.stdout etc.) are half torn > down already. It's really hard to prevent Python from emitting > the above exceptions, got a bit better with Python3 versions i think. > > best, > holger >
-- Anatoly Bubenkov _______________________________________________ Pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
