Python 3.12

[esc]

This ticket tracks overall progress of Python 3.12 support for Numba.

[esc]

A numba-hatchery based build using the python docker container is here:

numba/numba-hatchery#6

[esc]

A miniconda based variant of the hatchery is now here: numba/numba-hatchery#7 -- @kc611 @sklam @stuartarchibald and I are using this to port Numba to 3.12. I have begun to start collecting patches in my branch:

https://github.com/esc/numba/commits/py312

Note that this branch is still very much subject to frequent rebases, so do bear that in mind should you base anything off of it.

For those wondering about our timeline. A significant portion of the tests is working already and we are continuing to solve the issues we encounter from running the test-suite. At this stage things are looking OK, but Numba will not compatible from day 1 of the 3.12 release. As with 3.10 and 3.11 a Numba release supporting 3.12 will become available some time after the official release of 3.12.

[detrin]

I would love to see support for python3.12

[esc]

I would love to see support for python3.12

Yes, it's coming, soon. As of today, we are at around 98% of the test-suite passing and have roughly 100 failing tests left to fix.

[esc]

A draft PR has been opened: #9246 -- currently some tests are still failing, but the branch is OK enough for early testing.

[rupeshknn]

what's the ETA on this?

[esc]

what's the ETA on this?

Couple of weeks. According to my latest calculations, we are now at 12 errors and 28 failures remaining.

[kc611]

Pleased to announce that Numba 0.59.0 has been tagged and released along with official support for Python 3.12. 🎉

Closing this issue in accordance to the above.

[paddyroddy]

Pleased to announce that Numba 0.59.0 has been tagged and released along with official support for Python 3.12. 🎉

It doesn't seem to have been made into a release

[jorenham]

@paddyroddy Not on github, no. But it is available on pypi.

[jamesmyatt]

@paddyroddy Not on github, no. But it is available on pypi.

and conda-forge 👍

[esc]

@paddyroddy we don't prioritize releases on GitHub at the moment and crafting one is part of the post-release actions:

#9410

I've now fixed that:

https://github.com/numba/numba/releases/tag/0.59.0

And it's available:

@paddyroddy is this what you were asking about? Should we include making a "github-release" as part of the official release process rather than it being a post-release action? So far, there seems to have been little interest in "github-releases", but perhaps that is changing now?

[paddyroddy]

@esc I was merely wondering if it was an oversight. Personally, I don't mind either way. With my packages I usually make a release, which in itself pushes to PyPI - but my packages are far more trivial than numba, so I appreciate that it might not be possible that way.

[esc]

@esc I was merely wondering if it was an oversight. Personally, I don't mind either way. With my packages I usually make a release, which in itself pushes to PyPI - but my packages are far more trivial than numba, so I appreciate that it might not be possible that way.

Yes, I see, indeed our release process is quite complex. It involves several days of overnight testing and compiling packages on bare metal hardware and so on. We wouldn't be able to "just" make a GitHub release and have that be pushed to PyPi unfortunately. IIRC the delay of the "GitHub release" was mentioned as a criticism a few times before, so I will lobby to make that part of the release process, rather than it being a post-release action. Thank you!