Emergency Self-Construct
Emergency Self-Construct
> But I do have a question: what if I want to pass the keys by a numpy array? What numpy dtype is compatible with numba's unicode_type? I think I...
@M0gician I actually tried the following, and got stuck: ``` In [5]: @numba.njit ...: def function(): ...: s = 'δΈ' ...: a = np.array([s]) ...: return a ...: In [6]:...
@M0gician this was discussed in the developer meeting today and something fishy is going on here. This may be a Numba bug after all.
> Numpy only have one unicode type while numba has two, and it is totally unclear to me when and why numpy "U" type was casted to one numba unicode...
@arunoruto no
@Charis-E-Shiny thank you for submitting this improvement. Unfortunately the project is currently understaffed and we don't have an estimation as to when someone will be able to look at this.
> What is the target_triple for the system? Can you tell me the commands needed to discover that. I looked at: https://llvmlite.readthedocs.io/en/latest/user-guide/binding/target-information.html but then I only got: ``` $ python...
So I used: https://llvmlite.readthedocs.io/en/latest/user-guide/binding/target-information.html#llvmlite.binding.get_default_triple And this gave: ``` x86_64-pc-windows-msvc ```
I can also no longer reproduce this and your sentiment matches mine @yashssh @gmarkall @stuartarchibald.
@jorenham thank you for raising this. Numba pins Numpy (contrary to popular packaging advice) because Numpy releases are rarely backwards compatible with Numba. The next release of Numba --0.61 --...