python-pytest-twisted fails to build with Python 3.14.0b1. Creating the ticket for tracking purposes. twisted doesn't fully work with Python 3.14 yet. It was reported upstream. Failing twisted tests were skipped for now. But this causes python-pytest-twisted to fail, the fail comes from the codepath that is not prepared for Python 3.14. ======================== 52 passed, 8 skipped in 14.71s ======================== INTERNALERROR> Traceback (most recent call last): INTERNALERROR> File "/usr/lib/python3.14/site-packages/_pytest/main.py", line 279, in wrap_session INTERNALERROR> config._do_configure() INTERNALERROR> ~~~~~~~~~~~~~~~~~~~~^^ INTERNALERROR> File "/usr/lib/python3.14/site-packages/_pytest/config/__init__.py", line 1118, in _do_configure INTERNALERROR> self.hook.pytest_configure.call_historic(kwargs=dict(config=self)) INTERNALERROR> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.14/site-packages/pluggy/_hooks.py", line 535, in call_historic INTERNALERROR> res = self._hookexec(self.name, self._hookimpls.copy(), kwargs, False) INTERNALERROR> File "/usr/lib/python3.14/site-packages/pluggy/_manager.py", line 120, in _hookexec INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, firstresult) INTERNALERROR> ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 139, in _multicall INTERNALERROR> raise exception.with_traceback(exception.__traceback__) INTERNALERROR> File "/usr/lib/python3.14/site-packages/pluggy/_callers.py", line 103, in _multicall INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> File "/builddir/build/BUILD/python-pytest-twisted-1.14.3-build/BUILDROOT/usr/lib/python3.14/site-packages/pytest_twisted/__init__.py", line 472, in pytest_configure INTERNALERROR> reactor_installers[config.getoption("reactor")]() INTERNALERROR> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ INTERNALERROR> File "/builddir/build/BUILD/python-pytest-twisted-1.14.3-build/BUILDROOT/usr/lib/python3.14/site-packages/pytest_twisted/__init__.py", line 418, in init_asyncio_reactor INTERNALERROR> _install_reactor( INTERNALERROR> ~~~~~~~~~~~~~~~~^ INTERNALERROR> reactor_installer=asyncioreactor.install, INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> reactor_type=asyncioreactor.AsyncioSelectorReactor, INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> ) INTERNALERROR> ^ INTERNALERROR> File "/builddir/build/BUILD/python-pytest-twisted-1.14.3-build/BUILDROOT/usr/lib/python3.14/site-packages/pytest_twisted/__init__.py", line 434, in _install_reactor INTERNALERROR> reactor_installer() INTERNALERROR> ~~~~~~~~~~~~~~~~~^^ INTERNALERROR> File "/usr/lib/python3.14/site-packages/twisted/internet/asyncioreactor.py", line 304, in install INTERNALERROR> reactor = AsyncioSelectorReactor(eventloop) INTERNALERROR> File "/usr/lib/python3.14/site-packages/twisted/internet/asyncioreactor.py", line 50, in __init__ INTERNALERROR> _eventloop: AbstractEventLoop = get_event_loop() INTERNALERROR> ~~~~~~~~~~~~~~^^ INTERNALERROR> File "/usr/lib64/python3.14/asyncio/events.py", line 718, in get_event_loop INTERNALERROR> raise RuntimeError('There is no current event loop in thread %r.' INTERNALERROR> % threading.current_thread().name) INTERNALERROR> RuntimeError: There is no current event loop in thread 'MainThread'. 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-b1/fedora-rawhide-x86_64/09080895-python-pytest-twisted/ For all our attempts to build python-pytest-twisted with Python 3.14, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.14-b1/package/python-pytest-twisted/ 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-b1/ 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.
*** Bug 2372082 has been marked as a duplicate of this bug. ***
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 7+ weeks. This is the first reminder (step 3) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 4+ weeks. This is the second reminder (step 4) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
This package has been orphaned. You can pick it up at https://src.fedoraproject.org/rpms/python-pytest-twisted by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Automation has figured out the package is retired in rawhide. If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement