Bug 2327982 - python-jeepney fails to build with Python 3.14: RuntimeError: There is no current event loop in thread 'MainThread'.
Summary: python-jeepney fails to build with Python 3.14: RuntimeError: There is no cur...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-jeepney
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Göran Uddeborg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.14
TreeView+ depends on / blocked
 
Reported: 2024-11-22 10:10 UTC by Karolina Surma
Modified: 2025-03-04 15:32 UTC (History)
5 users (show)

Fixed In Version: python-jeepney-0.8.0-12.fc43 python-jeepney-0.9.0-1.fc43
Clone Of:
Environment:
Last Closed: 2025-02-25 13:02:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab takluyver jeepney issues 33 0 None opened In Python 3.14 asyncio.get_event_loop() no longer implicitly creates an event loop 2024-11-26 09:06:50 UTC

Description Karolina Surma 2024-11-22 10:10:13 UTC
python-jeepney fails to build with Python 3.14.0a2.

__________________________________ test_error __________________________________

    def test_error():
        router = Router(Future)
        call = message_bus.Hello()
>       future = router.outgoing(call)

jeepney/tests/test_routing.py:18: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
jeepney/routing.py:38: in outgoing
    self.awaiting_reply[msg.header.serial] = handle = self.handle_factory()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

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

    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 jeepney/tests/test_routing.py::test_message_reply - RuntimeError: Ther...
FAILED jeepney/tests/test_routing.py::test_error - RuntimeError: There is no ...
=================== 2 failed, 24 passed, 25 skipped in 0.14s ===================

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/08291807-python-jeepney/

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

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.

Comment 1 Göran Uddeborg 2024-11-26 09:06:50 UTC
I don't qualify myself, but I've created an upstreams issue to get the attention from the people who ACTUALLY know the package best. :-)

Comment 2 Fedora Update System 2025-02-25 11:22:53 UTC
FEDORA-2025-1e9476bbb2 (python-jeepney-0.8.0-12.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1e9476bbb2

Comment 3 Fedora Update System 2025-02-25 13:02:50 UTC
FEDORA-2025-1e9476bbb2 (python-jeepney-0.8.0-12.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2025-03-04 15:28:38 UTC
FEDORA-2025-a9890762c2 (python-jeepney-0.9.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a9890762c2

Comment 5 Fedora Update System 2025-03-04 15:32:54 UTC
FEDORA-2025-a9890762c2 (python-jeepney-0.9.0-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.