Nathan 'jesterKing' Letwory:
If you use Rhino 8 I’d stick with Python 3 instead of IronPython. With our Python 3 integration you get full access to .NET, including RhinoCommon
That all sounds fantastic. But in practice, besides breaking a lot of existing code and non-trivial hoop jumping (i.e. arising from direct .NET interop vs Python.NET
), it is painfully slow to use RhinoCommen with CPython 3:
Hi McNeel,
I’ve noticed that CPython scripts will perform substantially worse when implementing RhinoCommon than IronPython (presumably because of Python.NET) . And that the new script editor with IronPython performs slightly worse than GHPython (presumably because of the new editor, since they’re both running 2.7.12 .NETCoreApp). Here’s a quick demonstration making a whole bunch of Point3d within for loops:
[2024-02-05 14_54_27-Grasshopper - 230801_ScriptsMillionPoints_00_]
230801_ScriptsMi…
It’s just not there, yet
1 Like