I know there’s been an issue with IronPython compatibilities between independent installations and Rhino’s, and I’m wondering what best practices might be for dealing with it in the long term, on both the developer’s and user’s side.
Previous posts have directed to this troubleshooting page, but it isn’t clear how the fix should be interpreted for Rhino 6 or how to resolve conflicts for compiled .ghpy files in particular.
There’s a plugin we’ve been testing that throws a breakpoint error even if the independent IronPython is updated to 2.7.8 to match the Rhino version, and it isn’t clear under what circumstances (with any version of an independent installation) the plugin will load. Some fixes for a similar issue were discussed were discussed in this thread, but there doesn’t seem to be a general solution. Are there any rules we can follow to make this work consistently, or is it always a case-by-case matter depending on versions and contingencies?
Lastly, are there any future prospects for a broader way to address this? As people may have IronPython installed for a variety of reasons for other software (with Revit/Dynamo for sure), and it would be great to be able to distribute ghpy plugins in a reliable way.