-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.13 #9413
Comments
Great to see some steps towards 3.13 taking place - will numba publish PEP 703 free threading wheels ( |
RE: #9413 (comment)
We are talking about providing freethreading packages but the current priority is just to get through all the issues with bytecode changes. As of a8ad12a, the testsuite is at 493 failures out of 10385. |
As of 6cafffe, everything is working on py3.13 except for 3 failures that are unrelated to py3.13:
|
Basically the same as aaronzo said, but for PEP 738. |
Hi, I'm the maintainer of Chaquopy. Both myself and the Numba maintainers now work for Anaconda, so we'll hopefully be able to produce Numba builds for Python 3.13 on Android later in the year. But first we'll need to deal with more fundamental packages like NumPy. |
Think we need |
@jakirkham thanks for the reminder, there is now numba/llvmlite#1084 |
This issue is to track tasks and issues with Python 3.13.
Numba support status:
We gotnumba/tests/test_usecases.py
to pass. However, more involved tests are blocked by an issue with metaclass (Python 3.13.0a3 metaclass__call__
runs only once python/cpython#114806). As a result,Type._code
is not set properly. (temporary debug commit related to the issue: 4b6cc78)__call__
runs only once python/cpython#114806 is resolved. Continues to look into try-except changes 7/33 failures intest_try_except.py
The text was updated successfully, but these errors were encountered: