@joreg In my case one starts with importing the actual .py file. Then this generates all the function wrappers (marshalling from/to python) and adds the csproj+cs file to the active (focused) VL Document. Then I have a FileWatcher looking after this python file and will retrigger the cs wrapper generation, when the python file have been changed. This all works. So far, so good, but I need to know when this happens (inside my csproj // generated cs static class based on the python file), so I can call ReloadModule (this will reload the actual python file in the python environment/runtime) :). When I do that manually, it works well.
Any idea, how the v4 can inform the csproj, that it is about to be hot-reloaded and after it did that? This will solve my problem with reloading the same python module in the PythonRuntime. This I simulate as easy as calling init_module() in the generated csproj.
cheers