mrchem fails to build with Python 3.14.0a7.

+ /usr/bin/ctest --test-dir redhat-linux-build --output-on-failure --force-new-ctest-process -j1
Internal ctest changing into directory: /builddir/build/BUILD/mrchem-1.1.4-build/mrchem-1.1.4/redhat-linux-build
Test project /builddir/build/BUILD/mrchem-1.1.4-build/mrchem-1.1.4/redhat-linux-build
      Start 30: HF_molecular_gradient_LDA
 1/33 Test #30: HF_molecular_gradient_LDA ........***Failed    6.31 sec

running /builddir/build/BUILD/mrchem-1.1.4-build/mrchem-1.1.4/redhat-linux-build/bin/mrchem /builddir/build/BUILD/mrchem-1.1.4-build/mrchem-1.1.4/tests/hf_grad_lda/hf --executable=/builddir/build/BUILD/mrchem-1.1.4-build/mrchem-1.1.4/redhat-linux-build/bin/mrchem.x
test with input files /builddir/build/BUILD/mrchem-1.1.4-build/mrchem-1.1.4/tests/hf_grad_lda/hf and args None

stdout

stderr
/builddir/build/BUILD/mrchem-1.1.4-build/mrchem-1.1.4/python/mrchem/input_parser/plumbing/pyparsing/core.py:5332: SyntaxWarning: 'return' in a 'finally' block
  return self.__class__.__name__ + ": " + retString


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.


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

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

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.