Kay Hayen

So, it's not so much about order, but about the `PatchFinder` not knowing about the parent module yet, and its `__loader__` being responsible. There is code in Nuitka for when...

So I shifted the trick, but no success. The `__path__` and `sys.path_importer_cache` now list the loader, but the later seems unused for import purposes. I will need to trace the...

Ok, it's absolutely clear, I monkey patched the importlib and saw that it definitely wants to ask the package loader, which is us, to load anything below its path now....

This is part of the current hotfix release, turns out that do `sys.path` extension with names that should actually be in the module, and relative imports were not always followed,...

You can of course modify the source code, but that is a really important user request that nuitka by all means has to do that. Every time it failed to...

So, basically it is that you want to be like `CMD.EXE` yourself and catch and pass sigint at your discretion, that makes sense to me. You still will have ignore...

Renaming packages at run time like that, doesn't rename their children as well for Nuitka.

In this case, when you are replacing a module that is compiled with one that is as well, we could handle it, but not if you renamed it to something...

Well, for Nuitka any solution that involves code changes is bad, so I am never proposing it really. I think this kind of parent search is already being done in...

I don't think I want to start allowing this, code that does this, needs to be cleaned up to not do it.