python-fsleyes-widgets fails to build with Python 3.14.0a3. ________________________________ test_fileToUrl ________________________________ def test_fileToUrl(): # fname, expected testcases = [ '/home/blah/file.html' 'file.html', './file.html', '../file.html', ] for fname in testcases: expect = op.abspath(fname) expect = f'file://{expect}' > assert webpage.fileToUrl(fname) == expect E AssertionError: assert 'file:/home/b...htmlfile.html' == 'file:///home...htmlfile.html' E E - file:///home/blah/file.htmlfile.html E ? -- E + file:/home/blah/file.htmlfile.html 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/08480209-python-fsleyes-widgets/ For all our attempts to build python-fsleyes-widgets with Python 3.14, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-fsleyes-widgets/ 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.
Looks like https://github.com/python/cpython/issues/125974
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
Has been fixed in rawhide and stables releases. Closing.
We haven't seen a successful build yet, the test above still fails with Python 3.14.0b1.
Ankur, do you want to take care of reporting this upstream and, presumably, skipping the test for now? I would do it, but upstream uses a private GitLab instance at https://git.fmrib.ox.ac.uk/fsl/fsleyes/ that appears to be open only to affiliates of that particular lab at Oxford, so we can’t open an issue, and I just don’t feel like emailing the primary author right now.
*** Bug 2371914 has been marked as a duplicate of this bug. ***