Issues building ghpython

[ivelin.peychev]

@ivelin.peychev

After making them both appear in my GH can I compile ghpython(obsolete)component using ghpython(v6)?

To clarify what I meant.

Let’s say I build(compile) this:

GitHub - mcneel/ghpython: A Grasshopper component for Rhino.Python

Now I have both the new ghpython component and the old one.

Can I use the compiling-sdk.gh from this thread:

Tutorial: creating a Grasshopper component with the Python GHPY compiler

Hi @Mostapha I made changes to the compiling SDK and the last set of addition (ability to call from code the same compiler tool that is used in the wizard) is in the Rhino WIP of last week – 6.0.17010.13211. I am attaching here a definition that shows how that works. Please let me know if this is useful. [image] compiling-sdk.gh (14.0 KB)

In order to compile ghpython_old_component?

Reasons:

1. I want to not have to use clr.addreference for
   • DotNetZip.dll
   • MathNet.Numerics.dll
   • System.Xml.ReaderWriter.dll
   • TensorFlowSharp
   • etc.
2. I would like to make

import Grasshopper, GhPython

become this (as default)

import Grasshopper as gh
import GhPython
import scriptcontext as sc
from Grasshopper.Kernel import GH_RuntimeMessageLevel as RML

3. Another thing that I requested before is to make SDK mode as default, you said to make it another UserObject, could be done by simply changing the code.
4. Another one, re-arranging the code automatically when you click SDK mode. You know moving all imports together and moving the description comment on top, these kind of things.

If all of the above are not possible due to incompatibility, are you planning on releasing the source of the new ghpython so I can try to make these changes myself?