python-flake8 fails to build with Python 3.10.0a3. ==================================== ERRORS ==================================== ____________ ERROR collecting tests/unit/test_setuptools_command.py ____________ tests/unit/test_setuptools_command.py:3: in <module> from setuptools import dist /usr/lib/python3.10/site-packages/setuptools/__init__.py:16: in <module> import setuptools.version /usr/lib/python3.10/site-packages/setuptools/version.py:1: in <module> import pkg_resources /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() !!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!! =============================== 1 error in 0.64s =============================== error: Bad exit status from /var/tmp/rpm-tmp.MHoPFW (%check) Bad exit status from /var/tmp/rpm-tmp.MHoPFW (%check) For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.10/fedora-rawhide-x86_64/01826697-python-flake8/ For all our attempts to build python-flake8 with Python 3.10, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/python-flake8/ 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.
*** This bug has been marked as a duplicate of bug 1911607 ***