GitLab

The help() function was not working on wrapped class templates, so the
PyVTKTemplate type has been re-imagined as a module that contains the
instantiations of the template, since the help() function works with
module docstrings. PyVTKTemplate still supports the mapping protocol
as before, which allows lookup of the instantiated templates via the
template arguments.

Enum parameter types were missing from the python docstrings.  Also,
the PythonName utility function fits better in vtkWrapText.h.

This is done according to the documentation for PyTypeObject. It
allows python to correctly generate the __module__ attribute for
extension types, which is needed by some python packaging systems.

This is the first step towards Python 3 compatibility. Wrapped VTK classes
used to use the old-style python metaclass mechanism, and they worked like
the old-style classes from python 1 and python 2. Now each wrapped VTK
class is a new-style class with its own PyTypeObject.

Silences cppcheck warning.  Might have been a
false positive, but there’s no behaviour change.

Change-Id: I147eadb054d4cde44012fd8e8b9eb5e739eef6ad

Previously, enum types could only be used as method parameters if
the enum type was defined in the same class as the method.  This change
removes that restriction, by using the hierarchy files to figure out
what enum types will be wrapped across the whole project.

Change-Id: Ia44272a341312f984d05ed54ae3318c12a2fe404

The vtkParseHierarchy class was not detecting enum types, and the
vtkWrapPython_PythonicName code for converting mangled type names
to pythonic names was not able to handle namespaces.

Change-Id: If5c044eca741c12a387d150a764b65cf7085a4f9

Because several thousands lines of code is too much for one file.

Change-Id: Ib3af0f2153fddc3f593fd90913bb3408944062f6