Bug 2359525

python-ipyparallel fails to build with Python 3.14.0a7.

__________________ TestAsyncResult.test_display_output_error ___________________

self = <ipyparallel.tests.test_asyncresult.TestAsyncResult object at 0x7f1fe745eb70>

    def test_display_output_error(self):
        """display_outputs shows output on error"""
        self.minimum_engines(1)
    
        v = self.client[-1]
        ar = v.execute("print (5555)\n1/0")
        ar.get(5, return_exceptions=True)
        ar.wait_for_output(5)
        with capture_output() as io:
            ar.display_outputs()
>       assert io.stderr == ''
E       AssertionError: assert '/usr/lib/pyt...turn result\n' == ''
E         
E         + /usr/lib/python3.14/site-packages/IPython/core/interactiveshell.py:3139: SyntaxWarning: 'return' in a 'finally' block
E         +   return result

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

PEP 765: Disallow return/break/continue that exit a finally block
The compiler emits a SyntaxWarning when a return, break or continue statements appears where it exits a finally block.
This change is specified in PEP 765: https://peps.python.org/pep-0765/.

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/08900821-python-ipyparallel/

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

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.