Bug 2339094

python-behave fails to build with Python 3.14.0a4.

=================================== FAILURES ===================================
_______ TestAsyncContext.test_use_or_create_async_context__when_missing ________

self = <tests.api._test_async_step34.TestAsyncContext object at 0x7efccc5b1590>

    def test_use_or_create_async_context__when_missing(self):
        # -- CASE: AsynContext attribute is created with default_name
        context = self.make_context()
        context._push()
    
>       async_context = use_or_create_async_context(context)

tests/api/_test_async_step34.py:88: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
behave/api/async_step.py:279: in use_or_create_async_context
    async_context = AsyncContext(loop=loop, name=name, **kwargs)
behave/api/async_step.py:223: in __init__
    self.loop = loop or asyncio.get_event_loop() or asyncio.new_event_loop()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

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

    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:719: RuntimeError
________ TestAsyncContext.test_use_or_create_async_context__when_exists ________

self = <tests.api._test_async_step34.TestAsyncContext object at 0x7efccc5b16d0>

    def test_use_or_create_async_context__when_exists(self):
        # -- CASE: AsynContext attribute exists with default_name
        context = self.make_context()
>       async_context0 = context.async_context = AsyncContext()

tests/api/_test_async_step34.py:99: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
behave/api/async_step.py:223: in __init__
    self.loop = loop or asyncio.get_event_loop() or asyncio.new_event_loop()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

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

    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:719: RuntimeError

=========================== short test summary info ============================
FAILED tests/api/test_async_step.py::TestAsyncContext::test_use_or_create_async_context__when_missing
FAILED tests/api/test_async_step.py::TestAsyncContext::test_use_or_create_async_context__when_exists
======= 2 failed, 818 passed, 9 skipped, 2 xfailed, 2 warnings in 1.59s ========

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.)


https://docs.python.org/3.14/whatsnew/3.14.html

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

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

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.