Reloading Python code without restarting the FreeCAD

[Kunda1]

Related: https://github.com/FreeCAD/FreeCAD-addons/issues/159

[microelly2]

It would be handy for debugging if there was a button somewhere (or maybe just a "developer" menu item) that would allow you to force FreeCAD to reload a module(s).

You can hack your own reolad where you want.
But there cannot be a general solution.
If you have created python objects and you reload the class definitons you will get unexpected results or in worst case crashes.
So you should know what you do when you force a reload.

[aavogt]

I use sucessfully:

Code: Select all

import someModule
from importlib import reload
reload(someModule)

Based on the above, I put femloader.py and fem.py in ~/.local/share/FreeCAD/Macro/. After I save fem.py it gets reloaded automatically. I was hoping freecad would already do such a thing already since it will ask "This has been modified outside of the source editor. Do you want to reload it?" for .FCMacro files. So it can likely be done more portably (without pyinotify).

Code: Select all

# femloader.py
import sys
import os.path
sys.path += ["/usr/lib/python3/dist-packages/"] # why is this here for accessing ubuntu's python3-pyinotify?
import pyinotify
import fem
from importlib import reload

def reload_fem(event):
    reload(fem)
    print(f"reloaded fem from {event.pathname}")

def reloader():
    wm = pyinotify.WatchManager()
    femfile = os.path.join(os.path.dirname(__file__) , "fem.py")
    wm.add_watch(femfile, pyinotify.IN_MODIFY)
    notifier = pyinotify.ThreadedNotifier(wm, reload_fem)
    notifier.start()
    return notifier

notifier = reloader()

[onekk]

...
Based on the above, I put femloader.py and fem.py in ~/.local/share/FreeCAD/Macro/. After I save fem.py it gets reloaded automatically. I was hoping freecad would already do such a thing already since it will ask "This has been modified outside of the source editor. Do you want to reload it?" for .FCMacro files. So it can likely be done more portably (without pyinotify).

If you want to reply, open a new topic, you are necrobumping a 3yo topic.

Better not.

IMHO a macro is standalone file, not "multifile macros" as this is "out of scope" of a macro.

Regards

Carlo D.