Kay Hayen

While regular Numba JIT is now in fact something you can disable, it seems for librosa, we would have to have bytecode for at least this function, and maybe then...

For Tensorflow we are currently implementing JIT from source code, and it will be working for 2.2, and for Numba, I expect, we can do the same, having bytecode won't...

Thanks for your report, this is fixed 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...

Turns out, a change I made for Anaconda to not be affected, doesn't directly translate to Homebrew, where we need to find its installation path and it's not as `sys.prefix`...

This is part of the stable release 2.4 that I just made.

Since nothing is forthcoming and this cannot be reproduced for several reasons, I am closing this as invalid and will likely delete the issue later.

What is the alternative to `TMPDIR` for extracting and running an executable, then?!

Is there a `/var/tmp` on said system?

Well, you can always use `--onefile-temp-spec` and not use the temp folder, but e.g. a user cache folder, and if you want things to delete, just use a volatile value...

I agree, that would be sweet. In fact, executing binaries of course does not require the x bit at all. We could just as well load it and execute it...