- Jan 08, 2019
-
-
-
-
-
-
-
-
-
-
Ben Boeckel authored
These are better tracked directly by Git rather than as ExternalData.
-
Ben Boeckel authored
-
Ben Boeckel authored
-
-
-
-
-
-
-
Ben Boeckel authored
Data is now downloaded by each testing module as needed.
-
Ben Boeckel authored
-
Ben Boeckel authored
-
When a module is initialized, the 'depends' list for that module is now allowed to include the absolute path to each dependency, e.g. 'vtkmodule.vtkCommonCorePython'.
-
When the VTK Python extension modules are loaded more than once (e.g. by multiple Python interpreters in the same process), we must ignore any PyTypeObjects except for the ones from the first load. This fixes crashes that started occurring when we moved the PyTypeObjects from the shared PythonD libraries into the Python modules themselves.
-
This way, if one module depends on another, then it can check if that module has already been imported before calling ImportModule. In this way, people can avoid the ImportModule call completely by calling "import" themselves inside their Python code, which allows them to import the modules from a specific location.
-
If one vtk-python module depends on others, then it should load those dependencies before doing anything else.
-
This removes all of the PythonD libraries, and moves their contents into the python modules themselves. The result is a cleaner build.
-
If superclasses are linked via import, then it is no longer necessary for the dynamic linker to be able to find the superclass objects. This adds flexibility to the way the wrappers can be packaged.
-
For wrapped template specializations, the fully qualified name was added to the module dictionary, e.g. vtkCommonDataModelPython.name, instead of simply "name" by itself. This patch also removes some obsolete code for handling old-style classes, which were removed from the wrappers for Python3 and no longer need to be supported.
-
Ben Boeckel authored
-
-
-
-
-
-
-
-
-
-
-
-
-