Bug 2026354
| Summary: | python-spake2 fails to build with Python 3.11: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tomáš Hrnčiar <thrnciar> |
| Component: | python-spake2 | Assignee: | Fabio Valentini <decathorpe> |
| Status: | CLOSED DEFERRED | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | decathorpe, hugovk+redhatbugzilla, mhroncok, thrnciar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-02-10 08:56:31 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: | 2016048 | ||
Updating the bundled versioneer should fix this. Sorry for the late response. My E-Mail inbox is overflowing these days. I didn't know that this package bundled versioneer (whatever that is), so I'm not even sure how to start with updating it for this package. The versioneer python module on GitHub seems to be much different than the single file that's bundled with spake2. Any help would be much appreciated. Try following https://github.com/python-versioneer/python-versioneer#updating-versioneer (I do not appreciate the way versioneer is designed.) I will try that. Thanks for the pointer. This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36. Changes in configparser module were reverted in Python 3.11 and will be part of Python 3.12, thus I am closing this bugzilla. However, I highly encourage you to work with the upstream to fix it so we won't have to deal with it next year. Upstream issue: https://github.com/warner/python-spake2/issues/13 |
python-spake2 fails to build with Python 3.11.0a2. Traceback (most recent call last): File "/builddir/build/BUILD/spake2-0.8/setup.py", line 62, in <module> version=versioneer.get_version(), ^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/spake2-0.8/versioneer.py", line 1480, in get_version return get_versions()["version"] ^^^^^^^^^^^^^^ File "/builddir/build/BUILD/spake2-0.8/versioneer.py", line 1412, in get_versions cfg = get_config_from_root(root) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/spake2-0.8/versioneer.py", line 342, in get_config_from_root parser = configparser.SafeConfigParser() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'? Removed from the configparser module: the SafeConfigParser class, the filename property of the ParsingError class, the readfp() method of the ConfigParser class, deprecated since Python 3.2. (Contributed by Hugo van Kemenade in bpo-45173.) https://bugs.python.org/issue45173 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/02985724-python-spake2/ For all our attempts to build python-spake2 with Python 3.11, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/package/python-spake2/ 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.