Test suite failing under Python 3.14.0a4

[freakboy3742]

Describe the bug

Python 3.14.0a4 has just been released; it makes some changes to asyncio that cause the Rubicon test suite to fail:

_____________________ ERROR collecting tests/test_async.py _____________________
tests/test_async.py:7: in <module>
    from rubicon.objc.eventloop import EventLoopPolicy
.tox/py/lib/python3.14/site-packages/rubicon/objc/eventloop.py:659: in <module>
    class EventLoopPolicy(events.AbstractEventLoopPolicy):
E   AttributeError: module 'asyncio.events' has no attribute 'AbstractEventLoopPolicy'. Did you mean: 'AbstractEventLoop'?
=============================== warnings summary ===============================
.tox/py/lib/python3.14/site-packages/rubicon/objc/eventloop.py:6
.tox/py/lib/python3.14/site-packages/rubicon/objc/eventloop.py:6
  /Users/runner/work/rubicon-objc/rubicon-objc/.tox/py/lib/python3.14/site-packages/rubicon/objc/eventloop.py:6: DeprecationWarning: 'asyncio.DefaultEventLoopPolicy' is deprecated and slated for removal in Python 3.16
    from asyncio import (

Steps to reproduce

Run Rubicon's CI on Python 3.14.0a4

Expected behavior

Test suite should pass

Screenshots

No response

Environment

• Operating System: all
• Python version: 3.14.0a4+

Logs

Additional context

No response

[freakboy3742]

See python/cpython#127949 for the change that caused these failures.

It looks like there's an immediate workaround in using the _AbstractEventLoopPolicy alias; longer term (before the release of Python 3.16), we're going to need to adapt all usage of event loops to use direct instantiation instead of policy-based instantiation.