MAINT: Fix OMP warning coming from numba

[kp992]

Fixes #627
Fixes #729

I have tested locally and with the current main and pip install ., I get:

% python
Python 3.10.12 | packaged by conda-forge | (main, Jun 23 2023, 22:41:52) [Clang 15.0.7 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import quantecon
OMP: Info #276: omp_set_nested routine deprecated, please use omp_set_max_active_levels instead.

On this branch:

% python       
Python 3.10.12 | packaged by conda-forge | (main, Jun 23 2023, 22:41:52) [Clang 15.0.7 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import quantecon
>>>

[pep8speaks]

Hello @kp992! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2024-06-10 01:30:40 UTC

[kp992]

@mmcky Please check if this looks good to you.

[kp992]

Seems like CI needs fixing. Opened #731.

[coveralls]

coverage: 93.043% (+0.002%) from 93.041%
when pulling 79b9f63 on kp992:i-627
into bea8295 on QuantEcon:main.

[oyamad]

Thanks for taking care of this issue, but I think I am against changing the user's global setting in a library. What do you guys think?

[mmcky]

thanks @oyamad just diving into this myself.

I agree with @oyamad -- it is not generally a good idea to change global settings for users due to a package import. Is this controllable through checking numba versions and issuing a helpful message for switching it off? Is numba going to fix this warning message?

[oyamad]

There is an open PR numba/numba#7705; I don't know what its current status is (it has not been merged).