Bug 2325199

python-loguru fails to build with Python 3.14.0a1.

_______________________ test_caught_exception_queue_put ________________________

writer = <function writer.<locals>.w at 0x7f97163da350>
capsys = <_pytest.capture.CaptureFixture object at 0x7f97163acd50>

>   ???
E   AssertionError: assert False
E    +  where False = <built-in method endswith of str object at 0x7f971640afd0>('PicklingError: You shall not serialize me!')
E    +    where <built-in method endswith of str object at 0x7f971640afd0> = 'when serializing loguru._handler.Message object'.endswith

capsys     = <_pytest.capture.CaptureFixture object at 0x7f97163acd50>
err        = "--- Logging error in Loguru Handler #0 ---\nRecord was: {'elapsed': datetime.timedelta(seconds=1, microseconds=824540...alizing loguru._handler.Message state\nwhen serializing loguru._handler.Message object\n--- End of logging error ---\n"
lines      = ['--- Logging error in Loguru Handler #0 ---', "Record was: {'elapsed': datetime.timedelta(seconds=1, microseconds=824...7.2/loguru/_handler.py", line 204, in emit', '    self._queue.put(str_record)', '    ~~~~~~~~~~~~~~~^^^^^^^^^^^^', ...]
out        = ''
writer     = <function writer.<locals>.w at 0x7f97163da350>

tests/test_add_option_enqueue.py:104: AssertionError

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/08193984-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.