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
Surveying explicit uses of nopython=False
#9247
Comments
e.g., ``` ../../../../../opt/hostedtoolcache/Python/3.8.17/x64/lib/python3.8/site-packages/dist_matrix/utils/cpu_helper.py:99 /opt/hostedtoolcache/Python/3.8.17/x64/lib/python3.8/site-packages/dist_matrix/utils/cpu_helper.py:99: NumbaDeprecationWarning: The 'nopython' keyword argument was not supplied to the 'numba.jit' decorator. The implicit default value for this argument is currently False, but it will be changed to True in Numba 0.59.0. See https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-object-mode-fall-back-behaviour-when-using-jit for details. ```
Thank you for doing this! I opted to use the |
@crhea93
|
My use acse was old code that should probably be refactored to use the python object mode contexts, or simply |
objectmode context will mean nopython by default but manually opt into object mode in particular area (only inside the with-context) |
I think my use of |
#9352 has removed object mode fallback |
Numba plans to remove objectmode fallback in the 0.59 release. With the change,
nopython=False
will have no effect. We are surveying user code that usesnopython=False
instead of usingforceobj=True
. Perhaps it is due to bugs in Numba that prevent users from usingnopython=True
or a miscommunication from our deprecation notices. Either way, we need to understand why.Related issues:
The text was updated successfully, but these errors were encountered: