Bug 1818596
| Summary: | python-check-manifest fails to build with Python 3.9: No module named 'xml.etree.cElementTree' | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
| Component: | python-check-manifest | Assignee: | Fabian Affolter <mail> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | cstratak, mail, mhroncok, mplch |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-check-manifest-0.41-1.fc32 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-27 02:44:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1785415 | ||
FEDORA-2020-26c63131f4 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-26c63131f4 FEDORA-2020-26c63131f4 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-26c63131f4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-26c63131f4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-26c63131f4 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |
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.