Not sure if it’s a bug, but when I try to filter input values, it gets different result in python3 component.
The code is pretty simple:
if x%2 == 0:
a = x
else:
b = x
Not sure if it’s a bug, but when I try to filter input values, it gets different result in python3 component.
The code is pretty simple:
if x%2 == 0:
a = x
else:
b = x
@tpuaup Currently Grasshopper keeps the python scopes around between component runs and the previous value set to either a or b will be captured on the output. As in Dale’s example, assigning None to a or b explicitly solved the problem. But I see where the bug is and will fix that for 8.4
RH-79615 Unset outputs will use the persistent value from previous runs
RH-79615 is fixed in Rhino 8 Service Release 4 Release Candidate