Lock/Freeze RhinoCode Python environment

Grasshopper Developer
,
1

This issue is somewhat related to RhinoCode Inspector package override issue, but it seems better to me to discuss it separately.

We are struggling to getting the Python scripting component to work 100% reliably on ShapeDiver. The reason is that currently we can’t block package installations, which can cause the Python environment to be left behind in a corrupt state. Once this is so, Rhino has to be restarted and the Python environment has to be regenerated (all packages need to be reinstalled), which can take minutes to complete.

Once fix RH-88430 is out we should be able to completely block installation of new packages, i.e. corrupting the Python environment should become impossible by then. However, it would be great to have a way to completely freeze the Python environment, i.e. prevent any new package installation.

In addition we could significantly speed up the provisioning process of new EC2 instances for Rhino 8 if we were able to deploy the Python environment from a deployment bundle (a zip file), thereby avoiding the installation of Python packages on each new instance. This would be much faster, probably seconds instead of minutes. I guess this might work by creating a deployment bundle based on the %USERPROFILE%\.rhinocode directory prepared on another Windows machine. @eirannejad what do you think about this? Do you foresee any problems?

3

Hi Alex,

You can definitely zip-up the .rhinocode folder and deploy that. You can also configure Rhino to look for this directory in your own custom folder. See here

As for blocking package installs, the Inspector is the mechanism to do so currently. Let me know if the fix to RH-88430 works for you and removes the problem.

1 Like
4

Many thanks for this hint!

Just tested, the fix works great, thank you!

1 Like
5

Will this also work across Rhino 8 service releases? Or should we recreate the Python environment whenever we roll out a new service release and deploy both at the same time?

6

It should work across Rhino 8 service releases. We are not making any breaking changes to the runtime anymore at this point.

1 Like