Kay Hayen

You know, I never fix things by hand, if necessary, I do it with anti-bloat changes, but so far I believe this kind of JIT was at some point generally...

If you want to help, it would be better to spend you time maybe in this way: If you are available to do a PR, this can be fixed by...

Ah, the yaml can add instructions to include DLLs, it cannot fix cases, where dependencies fail to resolve. This resolution happens in the Python installation, not in the dist folder,...

I am revisiting this one in my attempts to get `numba` and `librosa` to work peacefully again. After adding support for JIT in #850 there is hope to resolve this,...

So, that `ImportError` was actually a bug in the lazy loader being parsed too late, only after its first user completed, and then never became resolved, but in that case,...

Then, the numba module `numba.np.ufunc.omppool` fails to find libomp on my system, which is normal, but Nuitka is crying out about it. Apparently numba handles this internally to fail to...

Now I am facing this one: > FATAL: Error, failed to find path @rpath/libsndfile.1.dylib (resolved DLL to /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/_soundfile_data/libsndfile.1.dylib) for /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/_soundfile_data/libsndfile_arm64.dylib from 'soundfile', please report the bug.

So, the path that aims to resolve this doesn't know how to gracefully handle the `.1` at the same time. It would accept the arm64 file only if it had...

It happens a lot that DLLs depends on versioned names of themselves and vice versa, and so does this DLL too. But i also needed to add the `_arm64` handling,...

Thanks for your report, this is worked on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html Feedback on...