python-pynacl fails to build with Python 3.14.0a1.

16 tests fail with the ImportError:

_____________________ ERROR collecting tests/test_utils.py _____________________
ImportError while importing test module '/builddir/build/BUILD/python-pynacl-1.5.0-build/pynacl-1.5.0/tests/test_utils.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.14/importlib/__init__.py:88: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/test_utils.py:18: in <module>
    import nacl.secret
../BUILDROOT/usr/lib64/python3.14/site-packages/nacl/secret.py:16: in <module>
    import nacl.bindings
../BUILDROOT/usr/lib64/python3.14/site-packages/nacl/bindings/__init__.py:186: in <module>
    from nacl.bindings.crypto_secretstream import (
../BUILDROOT/usr/lib64/python3.14/site-packages/nacl/bindings/crypto_secretstream.py:14: in <module>
    from typing import ByteString, Optional, Tuple, cast
E   ImportError: cannot import name 'ByteString' from 'typing' (/usr/lib64/python3.14/typing.py)

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

ByteString has been removed from both typing and collections.abc modules.
It had previously raised a DeprecationWarning since Python 3.12.


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/08189221-python-pynacl/

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

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.