Kay Hayen

There is currently no such option, this is hardcoded in Nuitka. We are planning to add this to the package configuration Yaml file, but that has not happened yet.

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 if...

The Python compilation of these modules should only happen once, and then the analysis result is cached, and bytecode directly created.

Feel free to read the User Manual if you have questions, esp. ones answered there. No C compilation will be done for these modules anymore, but there is a cache...

I believe the changes are in current stable through hotfixes, but not entirely sure, but due to the nature of the bug, let me close this, nothing happening there anymore.

The only point where a prior compilation can make a different to this, would be the caching of bytecode modules, which are once compiled for dependencies and then persisted. That...

I have not experienced a better reproducer so far, but I am sure I also saw it myself once. I will try and craft a case, where through a later...

It appears I lack the time to do this right now, but surely we ought to get to it. What we should do is to have a derived class for...

The developer prompt should only be used by people who know what they are doing. For mere mortals, a standard prompt is recommened. Then Nuitka (Scons) will find the right...

Let me know if that helps, I agree that what quote might have worked even with a development prompt, might be a regression there that these do not work at...