Bug 2155490 - libmodulemd fails to build with Python 3.12: RuntimeError: There is no current event loop in thread 'MainThread'.
Summary: libmodulemd fails to build with Python 3.12: RuntimeError: There is no curren...
Keywords:
Status: CLOSED DUPLICATE of bug 2155463
Alias: None
Product: Fedora
Classification: Fedora
Component: meson
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carl George 🎩
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.12
TreeView+ depends on / blocked
 
Reported: 2022-12-21 10:58 UTC by Tomáš Hrnčiar
Modified: 2022-12-21 14:02 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-21 14:02:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github mesonbuild meson issues 11204 0 None open 'meson test' fails to run on Python 3.12 2022-12-21 13:46:33 UTC

Description Tomáš Hrnčiar 2022-12-21 10:58:02 UTC
libmodulemd fails to build with Python 3.12.0a3.

Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/mesonbuild/mesonmain.py", line 194, in run
    return options.run_func(options)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/mesonbuild/mtest.py", line 2073, in run
    return th.doit()
           ^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/mesonbuild/mtest.py", line 1754, in doit
    self.run_tests(runners)
  File "/usr/lib/python3.12/site-packages/mesonbuild/mtest.py", line 1892, in run_tests
    loop = asyncio.get_event_loop()
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/asyncio/events.py", line 676, in get_event_loop
    raise RuntimeError('There is no current event loop in thread %r.'
RuntimeError: There is no current event loop in thread 'MainThread'.

asyncio.get_event_loop() and many other asyncio
functions like ensure_future(), shield() or gather(), and also the
get_event_loop() method of BaseDefaultEventLoopPolicy now raise a RuntimeError
if called when there is no running event loop and the current event loop was
not set. Previously they implicitly created and set a new current event loop.
DeprecationWarning is no longer emitted if there is no running event loop but
the current event loop is set in the policy. (Contributed by Serhiy Storchaka
in gh-93453.)

https://github.com/python/cpython/issues/93453

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

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.12/fedora-rawhide-x86_64/05133260-libmodulemd/

For all our attempts to build libmodulemd with Python 3.12, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/package/libmodulemd/

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.12:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/

Let us know here if you have any questions.

Python 3.12 is planned to be included in Fedora 39. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.12.
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 Stephen Gallagher 2022-12-21 13:46:34 UTC
The bug is actually in meson. See https://github.com/mesonbuild/meson/issues/11204

Comment 2 Miro Hrončok 2022-12-21 14:02:57 UTC

*** This bug has been marked as a duplicate of bug 2155463 ***


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