[issue33562] Check that the global settings for asyncio are not changed by tests

Change by Brett Cannon : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue33562] Check that the global settings for asyncio are not changed by tests

Brett Cannon added the comment: New changeset 8425de4147eb8d83befbb8ea77516fc764bb4309 by Brett Cannon in branch 'master': bpo-33562: Check the global asyncio event loop policy isn't set after any tests (GH-7328)

[issue33562] Check that the global settings for asyncio are not changed by tests

Change by Brett Cannon : -- pull_requests: +6957 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33562] Check that the global settings for asyncio are not changed by tests

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___

[issue33562] Check that the global settings for asyncio are not changed by tests

Change by Brett Cannon : -- keywords: +patch pull_requests: +6617 stage: -> patch review ___ Python tracker ___

[issue33562] Check that the global settings for asyncio are not changed by tests

New submission from Brett Cannon : There were not checks in test.libregrtest.save_env to make sure tests were not mucking with the default event loop. The settings to check seem to be: 'asyncio.get_event_loop_policy', 'asyncio.get_event_loop', 'asyncio_get_exception_handler',