Having the Python API made for some Extremely convenient processing. I really hope you considering supporting it in Wrap3 and future versions. I can’t understate this enough. For example, I could use external algorithms or scripts in Autodesk’s Maya for automating the process of finding corresponding points between shapes. For example I wrote an algorithm in Maya for detecting colored marker dots and finding corresponding marker names between different scans that are written to a text file that can be read into WrapX as pointOnTriangles (barycentric coords) instead of having to manually select them on both source and destination meshes. It was also convenient for using an automated process for finding corresponding freePolygon areas on the good/desirable geometry in places where there were holes in original scans. I could write those out as text files and read them into WrapX as a freePolygonIndicesFloating array parameter during nonRigidRegistration, ect… Mind you, I love your visual node based visual batch processing as an option, however I feel like much of the power of WrapX has been stripped away without the Python API. 
Please, please consider adding it. (P.S. Your Wrap programs rock!)
Cheers,
Spencer