> You don't need to replace the Python interpreter, run a separate compilation step, or even have a C/C++ compiler installed. Just apply one of the Numba decorators to your Python function, and Numba does the rest.
(Emphasis mine)
Also, I can't tell whether https://numba.readthedocs.io/en/stable/user/5minguide.html#w... implies that some code won't work, or won't get faster?
The argument of "some code won't get faster" is null, since you typically only want to use `@njit`, which ensures that you're in `nopython` mode.
I guess that's a double edged sword, in that when it says `nopython`, it really does mean no python.
This means you can only use features from the python interpreter that the numba team has re-implemented in LLVM IR.
---
IIRC `@njit` does involve an overhead in `lowering` the types from python -> LLVM when the first njit function in the call graph is invoked, but not after that.
All this means that if you use `for-loops` in nopython mode, they are guaranteed to run faster, at least in my experience.
https://numba.pydata.org/