Restart Fusion's Python Environment

[scruffmeister]

Hi,

During development of a reasonably complex script using multiple Python files, I am finding that when I make changes to method and object signatures I have to restart Fusion for it to pickup the changes. My project source is organised into folders under the script directory. Simple code changes within existing methods are picked up as you would expect.

I assume this behaviour is the consequence of some caching in the Python environment which is run by Fusion, whose lifetime spans script executions. Is there a way to force a restart/reload of Fusion's Python environment so that refactoring changes can be picked up without having to restart the entire Fusion application?

Thank you.

[0xHexdec]

Sems strange to me, as I havn't had this problem before. How to you restart your script? Do you use the debugger connected to Fusion to restart it, as this should make sure the project is up-to-date.

Do you load modules dynamically?

Dumb question, but if you use vscode, did you make sure to save the changes before running the script?

[borrinboing]

Hey, scruffmeister

I was having the exact same problem. It was a lot of frustration trying to fix a bug in my module before I realised my changes weren't being instantiated when re-running my original script... No idea why Fusion operates like this...

It's not elegant, but the work around I'm using is to have:

import importlib
import myModule
importlib.reload(myModule)

importlib allows you to forcibly reload modules and this will have to do while developing myModule.

Hope that helps.

I'm an OSX user, are you? It might be a unique Mac feature issue?

[JPKM20402]

I was having the same issue and it has been very frustrating.  The simple defined solution also worked for me within OSX.

[riik_b]

hey,

i had the same problems and i reloaded adsk.core and adsk.fusion after which it ran as it should, this was on windows. So thanks for the tip