Proximity3D flattens the results while using ghpython library

as in the topic. Why proximity3D function outputs flattened result when used with ghpython library? Nested lists are expected. . .
Is it a bug ? Any alternatives ?

Technically I can count the links’ (lines’) start points to get to know how many points are in the proximity, but anyway, somebody knows why?

Test failed with both gh 0.9.0076 and 1.0.0007.

Definition and screen attached.

Thanks in advance !
Gdańsk, Poland (11.7 KB)

Got around it with links’ repetitive start points counter. (green cloud results are the same). quite costy tho