python-beautifulsoup4 fails to build with Python 3.13.0a2.

This report is automated and not very verbose, but we'll try to get back here with details.

______________ TestLXMLXMLTreeBuilder.test_find_by_prefixed_name _______________

self = <bs4.tests.test_lxml.TestLXMLXMLTreeBuilder object at 0x7f86f8955d60>

        def test_find_by_prefixed_name(self):
            doc = """<?xml version="1.0" encoding="utf-8"?>
    <Document xmlns="http://example.com/ns0"
        xmlns:ns1="http://example.com/ns1"
        xmlns:ns2="http://example.com/ns2"
        <ns1:tag>foo</ns1:tag>
        <ns1:tag>bar</ns1:tag>
        <ns2:tag key="value">baz</ns2:tag>
    </Document>
    """
            soup = self.soup(doc)
    
            # There are three <tag> tags.
>           assert 3 == len(soup.find_all('tag'))
E           AssertionError

bs4/tests/__init__.py:1117: AssertionError
=========================== short test summary info ============================
FAILED bs4/tests/test_lxml.py::TestLXMLXMLTreeBuilder::test_find_by_prefixed_name
=================== 1 failed, 649 passed, 6 skipped in 3.19s ===================

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

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-rawhide-x86_64/06692169-python-beautifulsoup4/

For all our attempts to build python-beautifulsoup4 with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-beautifulsoup4/

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

Let us know here if you have any questions.

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