8000 gh-124694: In test_interpreter_pool, Restore the Asyncio Event Loop Policy During Cleanup by ericsnowcurrently · Pull Request #125708 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

gh-1 8000 24694: In test_interpreter_pool, Restore the Asyncio Event Loop Policy During Cleanup #125708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Oct 18, 2024
Merged

gh-124694: In test_interpreter_pool, Restore the Asyncio Event Loop Policy During Cleanup #125708

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
af52044
Clear the default event loop policy if it might have been set.
ericsnowcurrently Oct 18, 2024
b0519f9
Move the cleanup to the class teardown.
ericsnowcurrently Oct 18, 2024
216cc99
Add a comment about clearing the policy.
ericsnowcurrently Oct 18, 2024
0f6c50f
Update Lib/test/test_concurrent_futures/test_interpreter_pool.py
ericsnowcurrently Oct 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions Lib/test/test_concurrent_futures/test_interpreter_pool.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,6 +282,19 @@ def test_idle_thread_reuse(self):

class AsyncioTest(InterpretersMixin, testasyncio_utils.TestCase):

@classmethod
def setUpClass(cls):
# Most uses of asyncio will implicitly call set_event_loop_policy()
# with the default policy if a policy hasn't been set already.
# If that happens in a test, like here, we'll end up with a failure
# when --fail-env-changed is used. That's why the other tests that
# use asyncio are careful to set the policy back to None and why
# we're careful to do so here. We also validate that no other
# tests left a policy in place, just in case.
policy = support.maybe_get_event_loop_policy()
assert policy is None, policy
cls.addClassCleanup(lambda: asyncio.set_event_loop_policy(None))

def setUp(self):
super().setUp()
self.loop = asyncio.new_event_loop()
Expand Down
Loading
0