9591927
@@ -67,6 +67,10 @@
%prep
%forgeautosetup -p1
+ # seems to be fine with 3.11 but we need to loosen the guard
+ # see also: “python 3.10 support” https://github.com/numba/llvmlite/issues/740
+ sed -i 's/max_python_version =.*/max_python_version = "3.12"/' setup.py
+
# increase verbosity of tests to 2
sed -i 's/\(def run_tests.*verbosity=\)1/\12/' llvmlite/tests/__init__.py
Loosen the version guard even further to allow Python 3.11 so it can be tested in the Python 3.11 COPR.
Upstream issue for Python 3.10: https://github.com/numba/llvmlite/issues/740
A local mock build using the Python 3.11 COPR was successful.
Look here for a COPR build corresponding to this PR: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/builds/?dirname=python3.11:pr:1
This PR could be merged—but another valid approach would be to leave this PR open (and rebase as needed) to see if the build keeps succeeding in COPR or not (that is, if the version guard remains the only Python 3.11 incompatibility or not).
Note that, if we apply the upstream PR for Python 3.10 as a patch, we won’t have to loosen the version guard in the spec file for 3.10 anymore.
I went ahead and opened a PR for that.
rebased onto 8d5db64
rebased onto 9591927
Should we go ahead and do this? This PR still builds with Python 3.11, and it’s about one month until the mass Python rebuild in Rawhide.
Yeh, I think that should be OK :thumbsup:
Pull-Request has been merged by music
Loosen the version guard even further to allow Python 3.11 so it can be tested in the Python 3.11 COPR.
Upstream issue for Python 3.10: https://github.com/numba/llvmlite/issues/740
A local mock build using the Python 3.11 COPR was successful.