ScriptEditor or VS Code Project for Grasshopper Plugin

Thank you for such a thoughtful reply Callum. This helps me a lot.

I had made this other post a few days ago about one of those limitations (perhaps) that I’m running into with the ScriptEditor.

Is this issue one of those reasons for me to move to VS Code for a plugin project? It seems like my the libraries I’ve included in my ScriptEditor are indeed packaged in the Yak and extracted into the associated libs/ folder upon install, however the path’s don’t appear to be get automatically added to Python’s sys.path at runtime and currently my workaround is that I manually add them to sys.path anytime I change the code in the library. And this obviously doesn’t work for production. Not sure if I’ve phrased that all correctly.

The only similar issue I can find is maybe this…

Maybe you or someone on the team can confirm if that’s a bug or if I’m doing something incorrectly…

Thanks again, Callum!

1 Like