Skip to content
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

Track Changes in @jit in Numba Version0.59.0. #112

Open
HumphreyYang opened this issue Oct 11, 2023 · 5 comments · May be fixed by QuantEcon/lecture-python.myst#395
Open

Track Changes in @jit in Numba Version0.59.0. #112

HumphreyYang opened this issue Oct 11, 2023 · 5 comments · May be fixed by QuantEcon/lecture-python.myst#395
Assignees

Comments

@HumphreyYang
Copy link

From #294

@jstac:

Switch over to a simple @jit once 0.59 comes out

Keep track of changes in the deprecation of fall-back behaviour.

@mmcky
Copy link

mmcky commented Mar 4, 2024

I haven't seen the notices but our lectures are still using njit in
many cases, and probably jit(nopython=True) in a few cases.

See e.g., https://python-programming.quantecon.org/numba.html

@mmcky mmcky self-assigned this Mar 4, 2024
@jstac
Copy link
Contributor

jstac commented Mar 4, 2024

These substitutions should be straightforward but touch many lectures -- and hence need to be coordinated with @mmcky

@mmcky
Copy link

mmcky commented May 8, 2024

@HumphreyYang we have now updated all backends to use numba>=0.59 so I will add this to my list. Are there any examples that you know of that need updating?

@HumphreyYang
Copy link
Author

Many thanks @mmcky. The examples in my mind are cases involving @jit(nopython=True). I think we can simply change it to @jit. Here is an example where it is used: https://python.quantecon.org/mccall_model.html#implementation

@mmcky
Copy link

mmcky commented May 8, 2024

thanks @HumphreyYang I have opened a PR to review starting with lecture-python.myst

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants