python-libcst fails to build with Python 3.10.0b1. FAILED libcst/_nodes/tests/test_cst_node.py::CSTNodeTest::test_repr - Asserti... FAILED libcst/tests/test_tool.py::PrettyPrintNodesTest::test_full_tree - Asse... FAILED libcst/tests/test_tool.py::PrettyPrintNodesTest::test_hidden_syntax - ... FAILED libcst/tests/test_tool.py::PrettyPrintNodesTest::test_hidden_whitespace FAILED libcst/tests/test_tool.py::PrettyPrintNodesTest::test_hidden_whitespace_and_syntax The failures seem like differences in AST. For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.10/fedora-rawhide-x86_64/02174996-python-libcst/ For all our attempts to build python-libcst with Python 3.10, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/python-libcst/ 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 is a mass-posted update. Sorry if it is not 100% accurate to this bugzilla. The Python 3.10 rebuild is in progress in a Koji side tag. If you manage to fix the problem, please commit the fix in the rawhide branch, but don't build the package in regular rawhide. You can either build the package in the side tag, with: $ fedpkg build --target=f35-python Or you can the build and we will eventually build it for you. Note that the rebuild is still in progress, so not all (build) dependencies of this package might be available right away. Thanks. See also https://fedoraproject.org/wiki/Changes/Python3.10 If you have general questions about the rebuild, please use this mailing list thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/G47SGOYIQLRDTWGOSLSWERZSSHXDEDH5/
The f35-python side tag has been merged to Rawhide. From now on, build as you would normally build.
Put up https://src.fedoraproject.org/rpms/python-libcst/pull-request/2 to see if the new version works any better
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
FEDORA-2021-e905bc99eb has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e905bc99eb
FEDORA-2021-8114e33f99 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8114e33f99
FEDORA-2021-e905bc99eb has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e905bc99eb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e905bc99eb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8114e33f99 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8114e33f99` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8114e33f99 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8114e33f99 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-e905bc99eb has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.