[vtk-developers] Improvements to the Python wrapping in VTK

[Marcus D. Hanwell]

Hi,

I just pushed a topic to Gerrit (still marked as WIP) that attempts to
address several issues we perceived with the wrapping, such as
requiring both sources and headers when only headers are
wrapped/contain API, happening when the C++ classes are being built
when it should happen at the end using information exported that could
be used by any external or internal wrapping tool.

http://review.source.kitware.com/#/t/2340/

I think the name DoPython is lame, but nothing jumped out (suggestions
welcome). As far as I can see all of the Python tests still pass
(locally with fresh builds and on the CDash at Home submissions). This
also helps larger projects such as ParaView build against a system
installed (or at least previously built) VTK. We still need to add
some extra features such as installing the hints file, the module
information etc.

This also addresses several bugs we had noticed after the Python
wrapping was pushed into a module, as things like __init__.py need to
know about all wrapped modules in order to be built correctly. There
are still a few pieces to clean up, I would appreciate any thoughts on
what I might have missed too, ideally we would like to push all of the
wrapping to use this mechanism (client-server ParaView wrapping
already uses this approach).

Thanks,

Marcus