Implicit Cycles Preventing creating a Dictionary?

[AndersDeleuran]

@Jonathan_Hutchinson2

It looks like the rule of thumb, then, is that if I want to treat things ‘statically’ I need to do this input node trees >>> regular python types conversion.

It really depends on the case. But a good GHPython rule of thumb is to treat lists as lists and trees as trees explicitly (i.e. don’t use implicit cycles outside simple cases, there are more good reasons such as performance). For instance, in your case the keys could be a flat list and the code could be reduced to this:

230121_ToGHPythonDict_01.gh (13.3 KB)

@Jonathan_Hutchinson2

Does this relate to d[k[0]] = v ?

Yes that was it. I should have been more precise, my bad.

@Jonathan_Hutchinson2

… why do JSON and XML libraries not come up in the autocomplete for imports but they are available?

It’s a long story, see for instance this topic:

Importing IronPython libraries

The intellisense is named intelliclunk in Rhino for a good reason But just because a module doesn’t show up on import doesn’t mean you can’t use it. Unfortunately the help("modules") method doesn’t work in IronPython for listing all available Python modules. But you could do something like this to get an overview (note that this won’t list the available .NET libraries): [2020-04-17 09_31_25-Grasshopper - 200417_GHPython_GetIronPythonModules_00_] 200417_GHPython_GetIronPythonModules_00…