I have a plethora of errors in the past few days trying to revive a script. The major issue I am facing is that it seems any time a Honeybee component is attempting to load, it crashes Rhino/Grasshopper without any error log. One thing I found by locking the script containing legacy Honeybee components (and a healthy amount of research and troubleshooting) I noticed the crash always seems to involve components containing code for setting unique uids. (i.e. import uuid) Every single one of those components causes the crash as soon as it hits an unlocked canvas. Commenting out the line while the script is locked allows the component to exist on the canvas, and run, but without any of the dependencies to uuid.
Now, it gets a bit more interesting. To try troubleshooting further, I reinstalled nearly everything except Rhino. Same issue. I also downloaded LBT 1.1.0 to see if something stood out to me, which opened up a number of issues/trials to get those components to load, which I think I have gotten past most of including the issue of having to manually set the site_packages directory in Rhino (as I do have a company managed workstation). The interesting part is that after getting to the point where everything should be operational, I began to notice some of the Honeybee components of LBT 1.1.0 also immediately crash Rhino similar to the legacy crash I describe above.
So this is where I’m currently stuck. Is this an issue anyone has experienced? It seems like something is possibly wrong about the Python installations, which I attempted total re-installs. No change, and all other Python scripts I am using appear to work fine before and after. Or is this particular issue possibly due to a firewall program? (The company employs Sentinel which I saw a horror story about in another forum, and Grasshopper component folders had to be unprotected.) If that’s this issue, I have no management over that tool whatsoever.