Repository navigation
Python 3.11 #8304
Description
Activity
I'm making progress on the bytecode support at https://github.com/sklam/numba/tree/py3.11wip
- pinned this issue
on Oct 25, 2022 I'm making progress at #8545. The PR adapts Numba for the major bytecode changes in Py3.11.
Reacted by Zane Selvans, Brandon T. Willard, Benda Xu and PiReacted by Joren Hammudoglu, Pankaj Pandey, Jack McIvor, bjacklyn, Dominik Stańczak-Marikin, Konstantin Veretennicov, mhostetter, Ángel Velásquez, Erik Sundell and rkshthrmshReacted by Aristotelis Kittas, Fabio Mazza, Vitaly Bushaev and prodonly- added a commit that references this issue
on Nov 10, 2022 Still no official support for python 3.11 ?
Reacted by Vitaly Bushaev, Kamilake, tinyko, rs-pro0, Jari, Merlin Unterfinger, Ryan Dreifuerst, Ryan, Chang Ye, Jack McIvor and 26 more- added a commit that references this issue
on Nov 28, 2022 Any news?
There is an active https://github.com/numba/numba/commits/py3.11 branch, a lot of progress is happening.
@extesy thank you for listing that link. @alonme to answer your question: Indeed all the work for Python 3.11 is currently being merged one PR at a time to the
py3.11branch and collected there for further testing. IIRC @sklam mentioned during the last developer meeting (https://github.com/numba/numba/wiki/Minutes_2022_11_29) that there are only a handful of failing tests that remain. From what I can tell it shouldn't be long now and with any luck there will be a Numba release candidate that supports 3.11 before the end of the year 🤞 (but making no guarantees, obviously).Reacted by David CottrellReacted by Sylwester Arabas, James Myatt, Vitaly Bushaev, Bamdad Dashtban, Hailin Wang, Jack McIvor, Erik Sundell, x0s, Sara Neven, Martin Zapata and 1 moreThe changes needed to accommodate the majority of the new Python 3.11 op-code additions, along with changes to the op-code behaviour/sequences in the bytecode, have been addressed in #8545 and #8590 with thanks to @sklam. The majority of the remaining issues are addressed in #8639, a summary of the current state of the Numba test suite against this branch is here #8639 (comment) (less than 10 failures with varying degrees of difficulty to fix).
Reacted by David Cottrell- added a commit that references this issue
on Dec 6, 2022 We are providing a docker image for early testing Numba on Python 3.11. Please see details at: https://numba.discourse.group/t/ann-docker-image-for-early-testing-numba-on-python-3-11/1698
Reacted by teneon, Hailin Wang, Hantao Cui, eric-skydio and ShadowBoxingSkillsReacted by Dan Kelleher, Janos Gabler, Rodolfo De Nadai, Clemens Brunner, Jack McIvor, Alex Watson, Alexander Clausen, Nick Murphy and eric-skydio27 remaining items
hey @esc ,
so I understand this version won't be compatible with numpy>1.24, right? I know it may not be the place to ask but, can I know what's the problem with numpy >1.24 and when there will be a version for that? I never use numba, but just install a repo dependent on numba, and after having my project working in local and integrating in a bigger project I realized numba wasn't working with numpy 1.25, which is what we use in the other project... I installed 0.57.0dev0 to allow pip to install numba while having numpy > 1.24, but I got an error that I saw is related with numpy version in a different issue:
initialization of _internal failed without raising an exceptionThis issue is quite convoluted at this point, could one of the maintainers chime in and let the community know specifically what they need help with in terms of testing? We are all watching this issue but at this point it's not clear what needs to be tested to enable a release. (And we want to help! 😄 )
This issue is quite convoluted at this point, could one of the maintainers chime in and let the community know specifically what they need help with in terms of testing? We are all watching this issue but at this point it's not clear what needs to be tested to enable a release. (And we want to help! 😄 )
Sure, allow me to chime in! @sklam is currently still merging development branches and we are hoping to publish a release candidate next week (maybe the week after...). As soon the projects have been tagged and the build artifacts produced, we will be very grateful for everyone to test those candidates with their respective libraries and applications (and of course... to report back any encountered issues). An announcement with instructions on how to install will be posted to our discourse (numba.discourse.group) and will post a link here too, pointing everyone in the right direction.
Reacted by King Chung Huang, Yann ILAS, John Kerl, Infinoid, Nick Semenkovich, Michael Osthege, Krzysztof Kolasinski, Michael Moore, mattravel1, Jorge Martinez and 14 moreReacted by David Cottrell, Aristotelis Kittas, Michael Moore, Jorge Martinez, Daniel Stancl, soraros, Michael Dawson-Haggerty and RomanThe developers have my sympathies - I very much understand how using conda makes things easier - I hope to never have to install gdal without conda, and I can install independent versions of gcc with conda. Best of luck!
Py3.11 branch have been merged to main by #8822
Reacted by Emergency Self-Construct, Pankaj Pandey, ShadowBoxingSkills, Peter Jochem, Alex Watson, kristian, jakirkham, liudonghua, subsurfaceiodev, Mario Crespo and 9 moreReacted by Emergency Self-Construct and egeresReacted by Emergency Self-Construct, Joren Hammudoglu, Nick Murphy, Pankaj Pandey, Peter Jochem, Alex Watson, zanejgr, Yann ILAS, jakirkham, Qin and 8 moreReacted by Emergency Self-Construct, Jo Bovy, Bluesy1, Alex Watson, Alexander Steppke, Richard Kleijn, Krzysztof Kolasinski, egeres, J.J. van den Berg, soraros and 4 moreReacted by Emergency Self-Construct, Miguel, Philippe Miron, Bluesy1, Deepak Cherian, Nick Murphy, Be, Pankaj Pandey, Alex Watson, zanejgr and 13 moreWe are planning to cut an RC next week. Closing
Reacted by Jagtesh Chadha, Nick Murphy, Peter Jochem, Christian, Felix Williams, Bluesy1, Philippe Miron, jakirkham, stan-potums-smartaiconnect, Hailin Wang and 9 moreReacted by Jagtesh Chadha, Nick Murphy, Wei Ji, Thomas S. Binns, jakirkham, Hailin Wang, Krzysztof Kolasinski, Tan Tao-Lin and TuomoReacted by Nick Murphy, jakirkham, Michael Osthege, Hailin Wang, ysq151944 and TuomoIs there an issue to track updates on the RC and releases?
Is there an issue to track updates on the RC and releases?
A Release Candidate checklist for 0.57.0rc1 is now in #8841. Please do subscribe to that if you are interested in following progress. The official RC announcement will be made on the discourse forum as usual.
Reacted by James Myatt, jakirkham, Shantanu, Be, Tuomo, Nick Semenkovich, egeres, smorken, Johnny, Jon Barker and 9 more- unpinned this issue
on May 3, 2023 - added a commit that references this issue
on May 5, 2023 Python3.11 is supported from numba 0.57.0.
https://github.com/hauntsaninja/python_readiness
λ uv tool run python_readiness --python 3.11 --package numba numba>=0.57.0 # has_classifier_and_explicit_wheel
This is the meta/coordination issue for Python 3.11 support for Numba and llvmlite.
Note: The issue text will be updated continuously to reflect the current process and progress.
As Numba interfaces with cpython on the bytecode and C-level, Python minor version upgrades present a significant compatibility challenge and have -- in the past -- required multiple PRs over multiple months of work. For Python 3.11 this issue will serve as a central point of coordination of the efforts. As such it will list the current branches pertaining to Python 3.11 support in addition to using the tag
Python 3.11.In order to support testing against beta releases and release candidates, I created a small utility that allows easy setup of a Numba development environment against a Python pre-release docker container. https://github.com/numba/numba-hatchery this can be used with development branches/repositories of Numba and llvmlite.
llvmlite status
numba status
RESUMEopcode wasn't being handled. https://github.com/esc/numba/tree/python3.11_partial/implement_resume implements this.esc/python3.11now contains a merge of all involved feature branches and can be used for testing all required patches in unison: Python3.11 #8381TODO