Move numba.experimental to numba-extras

Edit by @gmarkall (2022-01-17): This issue records that we need to move functionality from the numba.experimental package to the numba-extras repo. Some discussion around related issues is also captured here.

---

Feature request

Hello all. I am opening this issue as a follow up to this: https://numba.discourse.group/t/numba-core-cpu-importing-stuff-from-numba-experimental/995

I am wondering if there is a better way to handle install_registry calls given. here: https://github.com/numba/numba/blob/6c95d38d945bb5ee77e52662bed416e24a2770ef/numba/core/cpu.py#L86

This is particularly causing a problem to me when I am bundling my package with pyinstaller(while having numba as a dependency). “_box” shared library file in numba.experimental.jitclass particularly causing trouble but I do not depend on any experimental feature and I am manually dropping experimental submodule to save the day. This is how I am handling things currently but I want to discuss here to see if we can have cleaner solutions on both end.

As far as I understood, experimental features meant to be for the users who want to use them and shouldn’t affect the stable API experience in the rest of the codebase. Aside from the inconvenience I am facing with pyinstaller, it can be useful to not import anything experimental unless user asks for it IMHO.

I can appreciate that this can be hard to resolve and I am happy to contribute as much as I can.

[gmarkall]

@AhmetCanSolak I think it’s OK to keep this issue - I’ve updated the title and made an edit to the description so it’s clear what we need to do - during the process of moving numba.experimental the person undertaking it might also want to consider why binaries in that module don’t get found by PyInstaller.

[AhmetCanSolak]

hello @gmarkall , are there any updates on this? anything I might be helpful with?