python-pylibmc fails to build with Python 3.11.0a2. Traceback (most recent call last): File "/builddir/build/BUILD/pylibmc-1.6.1/setup.py", line 98, in <module> with open("README.rst", "U", encoding="utf-8") as r: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ValueError: invalid mode: 'U' Changes in the Python API open(), io.open(), codecs.open() and fileinput.FileInput no longer accept 'U' (“universal newline”) in the file mode. This flag was deprecated since Python 3.3. In Python 3, the “universal newline” is used by default when a file is open in text mode. The newline parameter of open() controls how universal newlines works. (Contributed by Victor Stinner in bpo-37330.) https://bugs.python.org/issue37330 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/02941363-python-pylibmc/ For all our attempts to build python-pylibmc with Python 3.11, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/package/python-pylibmc/ 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.
Seems fixed: https://src.fedoraproject.org/rpms/python-pylibmc/c/f13c253722b6ce5f20072d65a3ec15f2fd9c0a17
This is FTBFS with Python 3.11 . I've fixed generic FTBFS with that update and build. I'll reopen this and close it once I backport the upstream commit fixing this issue (which isn't part of the latest upstream release: https://github.com/lericson/pylibmc/commit/22854a4ba8f7e926099219c107104723089bcad8#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7)
Fixed by python-pylibmc-1.6.1-2.fc36 .