python-parameterized fails to build with Python 3.11.0b2. ==================================== ERRORS ==================================== ___ ERROR at teardown of TestParameterizedClassDict_2_some_name.test_method ____ def tearDownModule(): missing = sorted(list(missing_tests)) > assert_equal(missing, []) E AssertionError: Lists differ: ["test_instance_method('foo0', bar=None)",[461 chars]o')"] != [] E E First list contains 12 additional elements. E First extra element 0: E "test_instance_method('foo0', bar=None)" E E + [] E - ["test_instance_method('foo0', bar=None)", E - "test_instance_method('foo1', bar=None)", E - "test_instance_method('foo2', bar=42)", E - 'test_instance_method(42, bar=None)', E - "test_mock_patch_standalone_function(42, 'umask')", E - "test_naked_function('foo0', bar=None)", E - "test_naked_function('foo1', bar=None)", E - "test_naked_function('foo2', bar=42)", E - 'test_naked_function(42, bar=None)', E - "test_patch_class_no_expand(42, 51, 'umask', 'getpid')", E - "test_patch_no_expand(42, 51, 'umask')", E - "test_wrapped_iterable_input('foo')"] parameterized/test.py:371: AssertionError https://docs.python.org/3.11/whatsnew/3.11.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.11/fedora-rawhide-x86_64/04481352-python-parameterized/ For all our attempts to build python-parameterized with Python 3.11, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/package/python-parameterized/ 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.11: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/ Let us know here if you have any questions. Python 3.11 is planned to be included in Fedora 37. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.11. 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 2059963 ***