New Py2 and Py3 treat empty tree branches differently than legacy Py

@eirannejad

When trying to copy paste a legacy python2 script to the new python2 component I found that it dealt with empty branches in a tree differently than the legacy.

The empty branches are ‘None’ in the new component and an empty list in the old one.

If a tree’s first 3 branches were empty…

Old Python2: [ [], [], [], ['some string', 'some string'] ]
New Python2: [ None, None, None, ['some string', 'some string'] ]

@ChristopherConnock Would you mind sending me an example that replicates this error?

@eirannejad

Here is an example. I added the new Python3 component, because it looks like it happens on all new Python components.

EmptyBranchExample.gh (13.7 KB)

I see. Thank you. I made this ticket and will get this fixed to be consistent.

RH-85932 New Py2 and Py3 treat empty tree branches differently than legacy Py

1 Like

FWIW the bug is with the Guid converter when using ghdoc Object type hint. It behaves correctly with ‘No type hint’

1 Like

RH-85932 is fixed in Rhino 8 Service Release 17 Release Candidate