Script Management

I’m running into issues managing different packages and their dependencies in Dynamo. For example, some packages I use rely on IronPython 2.7 (DynamoIronPython2.7 package, version 2.5.0), while others depend on newer versions. Since I can’t install multiple versions of the same package side by side, they end up conflicting with each other.

On top of that, a Python script that works on my system might fail on a colleague’s system cuz of slightly different Revit/Dynamo version, even when using the same engine. From what I understand, the IronPython 2 engine in Dynamo is tied to the DynamoIronPython2.7 package, but many other nodes rely on different versions of that package, which makes things even trickier.

I’ve been trying to migrate my scripts to CPython 3 or even IronPython 3, but my knowledge there is still limited. Honestly, I wish Dynamo made this simpler, just a straightforward visual programming environment without all the compatibility headaches.

Right now, it seems that building a custom add-in might actually be the more reliable long-term solution.

Any tips or suggestions are very welcome.

:raising_hands: Share your programming challenges, and we’ll help you migrate to a more up-to-date CPython 3 Dynamo. We’ll support you step-by-step to help you keep making progress. Hopefully, they aren’t too complex—the really tough ones will take more time, haha, Let’s go!

Over time most dynamo developers try to use less packages and depend on less in my experience. As you mentioned addins may eventually be more suitable unless you have a means of testing and managing at scale, e.g. Orkestra.

Journal automation for the win!

(graph 8 in the file which can be downloaded in this post)