That does indeed look like a version incompatibility between numba and numpy. I’d have expected that this would be fixed by switching to an older numpy. Can you double check that you get a compatible version with np.version.full_version?
I think (or at least really hope) that the new numba release that is compatible with the current numpy will be released very soon. So hopefully this problem will solve itself, in the meantime you can also try to install the release candidate. (see here for installation instructions).