Bug 2458662

python-dns fails to build with Python 3.15.0a8.

_______________ DNSSECMakeDSTestCase.testInvalidDigestLengthCDS0 _______________

self = <tests.test_dnssec.DNSSECMakeDSTestCase testMethod=testInvalidDigestLengthCDS0>

    def testInvalidDigestLengthCDS0(self):  # type: () -> None
        # Make sure the construction is working
        dns.rdata.from_text(dns.rdataclass.IN, dns.rdatatype.CDS, f"0 0 0 00")
    
        test_records = {
            "expecting another identifier": ["0 0 0", "0 0 0 "],
            "digest length inconsistent with digest type": ["0 0 0 0000"],
            "Odd-length string": ["0 0 0 0", "0 0 0 000"],
        }
        for msg, records in test_records.items():
            for record in records:
                with self.assertRaises(dns.exception.SyntaxError) as cm:
                    dns.rdata.from_text(dns.rdataclass.IN, dns.rdatatype.CDS, record)
>               self.assertEqual(msg, str(cm.exception))
E               AssertionError: 'Odd-length string' != 'Odd number of hexadecimal digits'
E               - Odd-length string
E               + Odd number of hexadecimal digits

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

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.15/fedora-rawhide-x86_64/10318675-python-dns/

For all our attempts to build python-dns with Python 3.15, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.15/package/python-dns/

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.15:
https://copr.fedorainfracloud.org/coprs/g/python/python3.15/

Let us know here if you have any questions.

Python 3.15 is planned to be included in Fedora 45.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.15.
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.