HDA python module bug

   382   1   1
User Avatar
Member
5 posts
Joined: Aug. 2015
Offline
Hi folks,

I'm developing a module to manage saving and versioning of HDAs.
I've noticed that when I save an HDA, if I previously performed a "Save Node Type" on another HDA, the default Python module gets overwritten by the one from the earlier save.

I suspect this is due to some kind of caching, does anyone know how to clear it?
I couldn't find any related topics, does this happen to you as well?

So far, the only workaround I've found is to rename the module so that each HDA has its own uniquely named module.
Do you know of any better workarounds?

Also, it seems that when using the createDigitalAsset function, there’s no way to pass a specific Python module to it.
When accessed from the HDA definition the module appears correct, but it still gets overwritten during the save process.

Cheers
User Avatar
Member
5 posts
Joined: Aug. 2015
Offline
Just bringing this up again; has anyone else run into this issue?

If it’s reproducible, I’m wondering if it makes sense to file a bug/RFE with SideFX.
  • Quick Links