Shapediver error in Python code using ghpythonlib.components

Hello, I have a problem with my Python script that uses basic Grasshopper components objects.

So this is my script: It runs series of calculations that end up in positions to be processed further by my GH script. besides that, the errors are sent to the viewer as text to display - which is the only way I am sort of able to debug the problem when uploaded to Shapediver.

Locally all works just fine in both Rhino 6 and Rhino 7. But when uploaded my file to Shapediver, the code encounters a problem on line 21:

But on line 21 of the scrip is only this:
" if vectorsXY[i][“vector”].Y > 0:"

“vectorsXY” is a list of vectors created as instances of the ghpythonlib.components.VectorXYZ() class. I feel I have no way of debugging this any further as everything works locally… I also found that not using the ghpythonlib.components solves the issue (I have to create my own classes for Points, Vectors, etc… and that is what I wanted to avoid if there is a way.

Is there a way to make it work without removing the object created as instances of ghpythonlib.components classes?
Is there something obvious that I am missing? :slight_smile:

I don’t think you are missing anything obvious, unless I am missing it too :slight_smile:

There seems to be an issue loading this dependency, probably because of a discrepancy between your local Rhino installation and the server configuration. Our team will look at this issue and get back to you.

Does ghpythonlib not work at all?
If it doesn’t work in general, we might be able to fix this, but here is an alternative:

I have went around it and created my own class Vector (I realized that the problem is in the way the vector coordinates are accessed by syntax from ghpythonlib: vector[“vector”] and in my class vector has directly accessible coordinates “vector.x” for example.

With this I am avoiding any access to the dictionaries created by the ghpythonlib and then my code works in ShapeDiver. :slight_smile:

I got my way around and hopefully you can identify, what is happening when it runs on Shapediver.