@ben.boeckel @dgobbi Thanks for your useful insights and advice.
We have a few other projects that relied on vtkWrapPython and I guess there are many others out there. Copy-pasting would work well in the short term, but it would be hard to maintain in the long term (we would end up with many slightly different variants of the script in various projects). What do you think about these options:
- Maintain vtkWrapPython macros in a separate repository
- Maintain the entire VTK\Wrapping folder and vtkWrapPython macros in a separate repository
- Add back vtkWrapPython macros to VTK with some automated tests to make sure they remain functional, even if VTK modules don’t rely on them (I know that @ben.boeckel wrote that this is not a preferred option but actually this seems to be the simplest and least amount of work overall)