python-check-manifest fails to build with Python 3.9.0a5.

==================================== ERRORS ====================================
__________________________ ERROR collecting tests.py ___________________________
tests.py:17: in <module>
    from xml.etree import cElementTree as ET
E   ImportError: cannot import name 'cElementTree' from 'xml.etree' (/usr/lib64/python3.9/xml/etree/__init__.py)
__________________________ ERROR collecting tests.py ___________________________
ImportError while importing test module '/builddir/build/BUILD/check-manifest-0.40/tests.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests.py:17: in <module>
    from xml.etree import cElementTree as ET
E   ImportError: cannot import name 'cElementTree' from 'xml.etree' (/usr/lib64/python3.9/xml/etree/__init__.py)
!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!
=========================== 2 error in 0.16 seconds ============================


See https://docs.python.org/3.9/whatsnew/3.9.html#removed

"The xml.etree.cElementTree module has been removed, use the xml.etree.ElementTree module instead. Since Python 3.3 the xml.etree.cElementTree module has been deprecated, the xml.etree.ElementTree module uses a fast implementation whenever available."



For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01322484-python-check-manifest/

For all our attempts to build python-check-manifest with Python 3.9, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/python-check-manifest/

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

Let us know here if you have any questions.

Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9.
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.