python-rx fails to build with Python 3.14.0a2.

_____ TestAsyncIOThreadSafeScheduler.test_asyncio_threadsafe_schedule_now ______

self = <tests.test_scheduler.test_eventloop.test_asynciothreadsafescheduler.TestAsyncIOThreadSafeScheduler testMethod=test_asyncio_threadsafe_schedule_now>

    def test_asyncio_threadsafe_schedule_now(self):
>       loop = asyncio.get_event_loop()

tests/test_scheduler/test_eventloop/test_asynciothreadsafescheduler.py:13: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = <asyncio.unix_events._UnixDefaultEventLoopPolicy object at 0x7f25e0d30d70>

    def get_event_loop(self):
        """Get the event loop for the current context.
    
        Returns an instance of EventLoop or raises an exception.
        """
        if self._local._loop is None:
>           raise RuntimeError('There is no current event loop in thread %r.'
                               % threading.current_thread().name)
E           RuntimeError: There is no current event loop in thread 'MainThread'.

/usr/lib64/python3.14/asyncio/events.py:681: RuntimeError

=========================== short test summary info ============================
FAILED tests/test_observable/test_flatmap_async.py::TestFlatMapAsync::test_flat_map_async
FAILED tests/test_observable/test_fromfuture.py::TestFromFuture::test_future_cancel
FAILED tests/test_observable/test_fromfuture.py::TestFromFuture::test_future_dispose
FAILED tests/test_observable/test_fromfuture.py::TestFromFuture::test_future_failure
FAILED tests/test_observable/test_fromfuture.py::TestFromFuture::test_future_success
FAILED tests/test_observable/test_start.py::TestStart::test_start_async - Run...
FAILED tests/test_observable/test_start.py::TestStart::test_start_async_error
FAILED tests/test_observable/test_tofuture.py::TestToFuture::test_await_empty_observable
FAILED tests/test_observable/test_tofuture.py::TestToFuture::test_await_error
FAILED tests/test_observable/test_tofuture.py::TestToFuture::test_await_success
FAILED tests/test_observable/test_tofuture.py::TestToFuture::test_await_success_on_sequence
FAILED tests/test_observable/test_tofuture.py::TestToFuture::test_await_with_delay
FAILED tests/test_observable/test_tofuture.py::TestToFuture::test_cancel - Ru...
FAILED tests/test_observable/test_tofuture.py::TestToFuture::test_dispose_on_cancel
FAILED tests/test_scheduler/test_eventloop/test_asyncioscheduler.py::TestAsyncIOScheduler::test_asyncio_schedule_action
FAILED tests/test_scheduler/test_eventloop/test_asyncioscheduler.py::TestAsyncIOScheduler::test_asyncio_schedule_action_cancel
FAILED tests/test_scheduler/test_eventloop/test_asyncioscheduler.py::TestAsyncIOScheduler::test_asyncio_schedule_action_due
FAILED tests/test_scheduler/test_eventloop/test_asyncioscheduler.py::TestAsyncIOScheduler::test_asyncio_schedule_now
FAILED tests/test_scheduler/test_eventloop/test_asynciothreadsafescheduler.py::TestAsyncIOThreadSafeScheduler::test_asyncio_threadsafe_schedule_action
FAILED tests/test_scheduler/test_eventloop/test_asynciothreadsafescheduler.py::TestAsyncIOThreadSafeScheduler::test_asyncio_threadsafe_schedule_action_cancel
FAILED tests/test_scheduler/test_eventloop/test_asynciothreadsafescheduler.py::TestAsyncIOThreadSafeScheduler::test_asyncio_threadsafe_schedule_action_due
FAILED tests/test_scheduler/test_eventloop/test_asynciothreadsafescheduler.py::TestAsyncIOThreadSafeScheduler::test_asyncio_threadsafe_schedule_now
======== 22 failed, 1300 passed, 10 skipped, 189714 warnings in 22.75s =========

According to https://docs.python.org/dev/whatsnew/3.14.html#id3

Removed implicit creation of event loop by asyncio.get_event_loop(). It now raises a RuntimeError if there is no current event loop. (Contributed by Kumar Aditya in gh-126353.)

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/08292734-python-rx/

For all our attempts to build python-rx with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-rx/

Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package builds with Python 3.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/

Let us know here if you have any questions.

Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires),
so if this package is required a lot, it's important for us to get it fixed soon.

We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work around it on our side.