Rhino/GH 8 Python initializer creates new Python directories

Rhino/Grasshopper gurus,

I’m experiencing an issue where a python component by Ladybug Tools (RUNUWG) sends data out to a standalone python instance within Windows, and while a python window appears, the normal verbose output and script appear to do nothing. A screenshot of the error and traceback are below.

A little bit more context, this started happening right appear restarting Rhino after attempting to use the new script editor within Rhino 8 which had the new pop-up indicating needs for installing python languages. That seemed fine at the time, however, it seems like these downloaded languages reassigned the default python library locations for Grasshopper, ignoring the ones used by Ladybug. Does that seem accurate to others?

This screen is checking the default Python library paths in Grasshopper, showing these .rhinoscript locations under my user folder.

In contrast, the Rhino PythonEditor does still show the library locations for Python I am used to having assigned. So this initializer also seems to have only affected Grasshopper.

Just FYI, I have reinstalled Ladybug Tools, the Rhino defaults txt file, and moved the Python libraries that Rhino is creating. I’m getting the same result.

Lastly, this does not seem to be causing any issues for the majority of grasshopper components that run in Python, just this one that is opening an external python console.

Thanks for bringing this up, @pdrake and sorry for the late response. In the future, you should post issues with Ladybug Tools to the LBT forum:

I likely would have seen this post much sooner had you posted there. I just pushed a fix for this case:

The fix is currently available via the LB Versioner component and will be in the next Ladybug Tools stable release.

Thanks again for reporting.