python-colcon-cmake fails to build with Python 3.10.0a3. ==================================== ERRORS ==================================== ______________ ERROR collecting test/test_parse_cmake_version.py _______________ test/test_parse_cmake_version.py:4: in <module> from colcon_cmake.task.cmake import _parse_cmake_version_string colcon_cmake/task/cmake/__init__.py:12: in <module> from pkg_resources import parse_version /usr/lib/python3.10/site-packages/pkg_resources/__init__.py:73: in <module> from pkg_resources.extern import appdirs <frozen importlib._bootstrap>:1026: in _find_and_load ??? <frozen importlib._bootstrap>:1005: in _find_and_load_unlocked ??? <frozen importlib._bootstrap>:681: in _load_unlocked ??? E ImportWarning: VendorImporter.exec_module() not found; falling back to load_module() =========================== short test summary info ============================ ERROR test/test_parse_cmake_version.py - ImportWarning: VendorImporter.exec_m... !!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!! =============================== 1 error in 0.20s =============================== For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.10/fedora-rawhide-x86_64/01824051-python-colcon-cmake/ For all our attempts to build python-colcon-cmake with Python 3.10, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/python-colcon-cmake/ 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.10: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/ Let us know here if you have any questions. Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10. 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.
I've added the upstream ticket tracking this issue in setuptools. There is a workaround to get the tests passing, but the ticket is fairly fresh, and I'd like to give it some time to mature.
*** This bug has been marked as a duplicate of bug 1911607 ***