Can I take it up for packaging?

Not yet working with llvm10: https://github.com/numba/llvmlite/issues/583

Looks like it doesn't support 3.10 yet :crying_cat_face:

Even their git, on the master branch, doesn't do 3.10 yet:

https://github.com/numba/numba/blob/master/setup.py

I bumped up the max_python version and ran into compilation errors. I'll look into them later to see if we can submit patches etc.

Looks like Python 3.9 support took four months after Python 3.9 was released.

Upstream is starting a little earlier for Python 3.10. Here is a work-in-progress PR for Python 3.10, and this says that the numba 0.55 RC is scheduled for early October, around the time Python 3.10 is released.

It’s going to be a challenge to line this package up with Python and Fedora release schedules.

Yeh, the error I'm getting could also be a python regression, so filed this in the meantime:

https://bugzilla.redhat.com/show_bug.cgi?id=2005686

we have 3.10 support now, but not 3.11 (which is default in rawhide now?)

https://github.com/numba/numba/blob/main/setup.py#L23

It feels like this is always going to be lagging the version of python we use in rawhide because we adopt newer versions earlier, so there's going to be a really tiny window between numba supporting a python version and fedora moving on to the next one where we can include this---but then it'll remain broken in rawhide for a while after we move to the new python version until numba catch up

numba 3.11 progress: https://github.com/numba/numba/issues/8304

we have 3.10 support now, but not 3.11 (which is default in rawhide now?)

https://github.com/numba/numba/blob/main/setup.py#L23

It feels like this is always going to be lagging the version of python we use in rawhide because we adopt newer versions earlier, so there's going to be a really tiny window between numba supporting a python version and fedora moving on to the next one where we can include this---but then it'll remain broken in rawhide for a while after we move to the new python version until numba catch up

Even that may not be good enough. That would be the situation if, like Fedora, Numba were tracking Python pre-releases and trying to release support close to the final release. I’ve lost the link, but upstream indicates that three to six months is normally needed after the final release of a new Python minor version, which happens about the same time as the first Fedora release containing it. So the clock started ticking on Python 3.11 support when it was released on 2022-10-24; and we released Fedora 37 with Python 3.11 a few weeks later on 2022-11-15. Right now, Numba upstream is about to finish Python 3.11 support; meanwhile Fedora 38 is in beta. That’s an entire Fedora release cycle where Numba doesn’t support the system Python. Basically, we would have a working Numba package in every other Fedora release, which would wreak havoc on dependent packages.