Bug 2345523 - python-loguru fails to build with Python 3.14: DeprecationWarning: 'asyncio.set_event_loop' is deprecated and slated for removal in Python 3.16
Summary: python-loguru fails to build with Python 3.14: DeprecationWarning: 'asyncio.s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-loguru
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Beasley
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.14
TreeView+ depends on / blocked
 
Reported: 2025-02-13 11:33 UTC by Karolina Surma
Modified: 2025-02-13 13:31 UTC (History)
4 users (show)

Fixed In Version: python-loguru-0.7.3-4.fc43
Clone Of:
Environment:
Last Closed: 2025-02-13 13:31:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github Delgan loguru issues 1296 0 None open Python 3.14: test_global_loop_not_used fails due to DeprecationWarning for asyncio.set_event_loop 2025-02-13 13:12:09 UTC

Description Karolina Surma 2025-02-13 11:33:36 UTC
python-loguru fails to build with Python 3.14.05.

__________________________ test_global_loop_not_used ___________________________

capsys = <_pytest.capture.CaptureFixture object at 0x7f6dbe074f30>

>   ???

capsys     = <_pytest.capture.CaptureFixture object at 0x7f6dbe074f30>
loop       = <_UnixSelectorEventLoop running=False closed=True debug=False>

tests/test_coroutine_sink.py:167: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib64/python3.14/contextlib.py:141: in __enter__
    return next(self.gen)
        self       = <contextlib._GeneratorContextManager object at 0x7f6dbe3bf8c0>
tests/conftest.py:97: in set_event_loop_context
    asyncio.set_event_loop(loop)
        loop       = <_UnixSelectorEventLoop running=False closed=True debug=False>
/usr/lib64/python3.14/asyncio/events.py:843: in set_event_loop
    warnings._deprecated('asyncio.set_event_loop', remove=(3,16))
        loop       = <_UnixSelectorEventLoop running=False closed=True debug=False>
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

name = 'asyncio.set_event_loop'
message = '{name!r} is deprecated and slated for removal in Python {remove}'

    def _deprecated(name, message=_DEPRECATED_MSG, *, remove, _version=sys.version_info):
        """Warn that *name* is deprecated or should be removed.
    
        RuntimeError is raised if *remove* specifies a major/minor tuple older than
        the current Python version or the same version but past the alpha.
    
        The *message* argument is formatted with *name* and *remove* as a Python
        version tuple (e.g. (3, 11)).
    
        """
        remove_formatted = f"{remove[0]}.{remove[1]}"
        if (_version[:2] > remove) or (_version[:2] == remove and _version[3] != "alpha"):
            msg = f"{name!r} was slated for removal after Python {remove_formatted} alpha"
            raise RuntimeError(msg)
        else:
            msg = message.format(name=name, remove=remove_formatted)
>           warn(msg, DeprecationWarning, stacklevel=3)
E           DeprecationWarning: 'asyncio.set_event_loop' is deprecated and slated for removal in Python 3.16

_version   = sys.version_info(major=3, minor=14, micro=0, releaselevel='alpha', serial=5)
message    = '{name!r} is deprecated and slated for removal in Python {remove}'
msg        = "'asyncio.set_event_loop' is deprecated and slated for removal in Python 3.16"
name       = 'asyncio.set_event_loop'
remove     = (3, 16)
remove_formatted = '3.16'

/usr/lib64/python3.14/warnings.py:677: DeprecationWarning

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

asyncio policy system is deprecated and will be removed in Python 3.16. In particular, the following classes and functions are deprecated:
asyncio.AbstractEventLoopPolicy
asyncio.DefaultEventLoopPolicy
asyncio.WindowsSelectorEventLoopPolicy
asyncio.WindowsProactorEventLoopPolicy
asyncio.get_event_loop_policy()
asyncio.set_event_loop_policy()
asyncio.set_event_loop()
Users should use asyncio.run() or asyncio.Runner with loop_factory to use the desired event loop implementation.)


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/08651031-python-loguru/

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

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 Ben Beasley 2025-02-13 13:12:10 UTC
This DeprecationWarning is a useful advance notice of future incompatibility, but does not reflect a current defect for Python 3.14. I reported it upstream in https://github.com/Delgan/loguru/issues/1296, and I plan to use a warnings filter to ignore it downstream.

Comment 2 Fedora Update System 2025-02-13 13:28:36 UTC
FEDORA-2025-64cfefd81a (python-loguru-0.7.3-4.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-64cfefd81a

Comment 3 Fedora Update System 2025-02-13 13:31:40 UTC
FEDORA-2025-64cfefd81a (python-loguru-0.7.3-4.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.