Python Meshlib v3.0.1.205 issues

[emil-peters]

Hi all,

I've been looking at using the new meshlib python build, but due to the automatic conversion, there are a lot of typing issues we're now having with types previously defined.

mr.vectorEdgePath = mr.std_vector_std_vector_Id_EdgeTag

And some issues with functions no longer existing 🤔

Can't execute: 
`mr.getLargestComponentVerts`

I'll experiment some more next week to see if I can find any other inconsistencies

[Grantim]

Hello!

We have added some aliases for complex types

>>> from meshlib import mrmeshpy as mm
>>> help(mm.std_vector_std_vector_Id_EdgeTag)
Help on class std_vector_std_vector_Id_EdgeTag in module meshlib.mrmeshpy:

class std_vector_std_vector_Id_EdgeTag(pybind11_builtins.pybind11_object)
 |  Aliases:  std_vector_EdgeLoop, EdgeLoops, std_vector_EdgeLoop, std_vector_EdgePath, std_vector_EdgePath, std_vector_EdgePath, std_vector_EdgeLoop

Also c++ namespaces are now respected in python bindings

from meshlib import mrmeshpy as mr
mr.getLargestComponentVerts = mr.MeshComponents.getLargestComponentVerts

If you know c++ analogue for missing function you can find it with same name in python (if not please let us know)